Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
Problem starting docker
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Installing Gentoo
View previous topic :: View next topic  
Author Message
leonchik1976
Apprentice
Apprentice


Joined: 24 Jan 2010
Posts: 169

PostPosted: Fri Jan 13, 2017 8:52 am    Post subject: Problem starting docker Reply with quote

i'm trying to install docker, but when i try to start it, i have the following errors, any ideas?
Code:

gserver ~ # docker run --rm hello-world
container_linux.go:247: starting container process caused "process_linux.go:359: container init caused \"rootfs_linux.go:53: mounting \\\"cgroup\\\" to rootfs \\\"/var/lib/docker/devicemapper/mnt/b79c12d374aef5503ff36ff60a550d56ed8e0b06efd84723026fb5093c001520/rootfs\\\" at \\\"/sys/fs/cgroup\\\" caused \\\"no subsystem for mount\\\"\""
docker: Error response from daemon: containerd: container not started.

gserver ~ # systemctl status docker.service
● docker.service - Docker Application Container Engine
   Loaded: loaded (/usr/lib/systemd/system/docker.service; disabled; vendor preset: disabled)
   Active: active (running) since Fri 2017-01-13 10:51:00 IST; 21s ago
     Docs: https://docs.docker.com
 Main PID: 2128 (dockerd)
    Tasks: 21 (limit: 4915)
   Memory: 59.4M
      CPU: 1.497s
   CGroup: /system.slice/docker.service
           ├─2128 /usr/bin/dockerd -H fd://
           └─2153 docker-containerd -l unix:///var/run/docker/libcontainerd/docker-containerd.sock --metrics-interval=0 --start-timeout 2m --state-dir /var/run/docker/libcontainerd/containerd --shim docker-containerd-shim --ru

Jan 13 10:51:00 gserver dockerd[2128]: time="2017-01-13T10:51:00.175032343+02:00" level=info msg="Default bridge (docker0) is assigned with an IP address 172.17.0.0/16. Daemon option --bip can be used to set a preferred IP add
Jan 13 10:51:00 gserver dockerd[2128]: time="2017-01-13T10:51:00.209855871+02:00" level=info msg="Loading containers: done."
Jan 13 10:51:00 gserver dockerd[2128]: time="2017-01-13T10:51:00.323221241+02:00" level=warning msg="failed to retrieve docker-init version: unknown output format: tini version 0.13.2\n"
Jan 13 10:51:00 gserver dockerd[2128]: time="2017-01-13T10:51:00.325148857+02:00" level=info msg="Daemon has completed initialization"
Jan 13 10:51:00 gserver dockerd[2128]: time="2017-01-13T10:51:00.325466616+02:00" level=info msg="Docker daemon" commit=2f2d055 graphdriver=devicemapper version=1.13.0-rc6
Jan 13 10:51:00 gserver dockerd[2128]: time="2017-01-13T10:51:00.363504247+02:00" level=info msg="API listen on /var/run/docker.sock"
Jan 13 10:51:00 gserver systemd[1]: Started Docker Application Container Engine.
Jan 13 10:51:12 gserver dockerd[2128]: time="2017-01-13T10:51:11.535658696+02:00" level=error msg="containerd: start container" error="containerd: container not started" id=26ef335cbe62e802e34fb7454b2619099bc1528bb606ec5428a66
Jan 13 10:51:12 gserver dockerd[2128]: time="2017-01-13T10:51:11.537195105+02:00" level=error msg="Create container failed with error: containerd: container not started"
Jan 13 10:51:13 gserver dockerd[2128]: time="2017-01-13T10:51:13.859786254+02:00" level=error msg="Handler for POST /v1.25/containers/26ef335cbe62e802e34fb7454b2619099bc1528bb606ec5428a6628d85bd403d/start returned error: conta


[Moderator edit: added [code] tags to preserve output layout. -Hu]
Back to top
View user's profile Send private message
Hamlet
Tux's lil' helper
Tux's lil' helper


Joined: 15 Apr 2005
Posts: 133
Location: Turin (Italy)

PostPosted: Sat Jan 21, 2017 7:54 am    Post subject: Reply with quote

I have the same problem.
Code:
$ docker info
Containers: 0
 Running: 0
 Paused: 0
 Stopped: 0
Images: 1
Server Version: 1.13.0-rc7
Storage Driver: overlay2
 Backing Filesystem: reiserfs
 Supports d_type: false
 Native Overlay Diff: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: bridge host macvlan null overlay
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: v0.2.5 (expected: 03e5862ec0d8d3b3f750e19fca3ee367e13c090e)
runc version: c91b5be (expected: 2f7393a47307a16f8cee44a37b262e8b81021e3e)
init version: N/A (expected: 949e6facb77383876aeff8a6944dde66b3089574)
Security Options:
 seccomp
  Profile: default
Kernel Version: 4.9.3-gentoo
Operating System: Gentoo/Linux
OSType: linux
Architecture: x86_64
CPUs: 8
Total Memory: 15.56 GiB
Name: glamis
ID: 7X5A:GLGZ:J7WA:2RWE:LGT5:AD6O:N43K:JYZO:3VRQ:DORZ:PISW:7G7J
Docker Root Dir: /mnt/VMs/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
Experimental: false
Insecure Registries:
 127.0.0.0/8                                                                                                                                                                                                     
Live Restore Enabled: false

The check-config.sh script is fairly happy:
Code:
$ /usr/share/docker/contrib/check-config.sh
Optional Features:
[...]
- CONFIG_EXT3_FS_XATTR: missing
[...]
- Storage Drivers:
  - "aufs":
    - CONFIG_AUFS_FS: missing
[...]
  - "zfs":
    - /dev/zfs: missing
    - zfs command: missing
    - zpool command: missing

The ones above are the only missing things, and my kernel does not have those features any more (and emerging zfs fails, which I can live with).
I have moved the "root dir" to a different location (reiserfs), but with the default one (ext4) the problem still persists.
Also, the problem persists with both a normal user (in "docker" group) and with the administrator (root).
And I have sys-apps/systemd-232 running.
Back to top
View user's profile Send private message
Hamlet
Tux's lil' helper
Tux's lil' helper


Joined: 15 Apr 2005
Posts: 133
Location: Turin (Italy)

PostPosted: Sat Jan 21, 2017 5:44 pm    Post subject: Reply with quote

The link to the opencontainer issue explains a workaround.
Apparently the Control Groups system has been recently revamped (at kernel 4.5 according to the manual, `man 7 cgroups`), and my understanding is that systemd hasn't figured out completely yet how to work with it.
I report here the workaround suggested there, that seems to instruct Linux to use the legacy CGroups code for systemd, by adding to /etc/default/grub
Code:
GRUB_CMDLINE_LINUX_DEFAULT="systemd.legacy_systemd_cgroup_controller=yes"

(I changed GRUB_CMDLINE_LINUX instead... and I don't even remember why I preferred to do so) and then regenerating the grub configuration in the usual way (that I think is something like grub-mkconfig). A reboot is then required with the new setting.
This makes the hello-world container run on my system (`docker run --rm hello-world`).
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Installing Gentoo All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum