Docker cannot start the container ... cpu.shares: no such file or directory

When I try to launch the docker image, I get the following error:

Error response from daemon: Cannot start container {id}: [8] System error: open /sys/fs/cgroup/cpu,cpuacct/init.scope/system.slice/docker-{id}.scope/cpu.shares: no such file or directory 

/sys/fs/cgroup/cpu,cpuacct/ , but in init.scope

no system.slice directory

docker version:

 Client version: 1.7.1 Client API version: 1.19 Go version (client): go1.4.2 Git commit (client): 786b29d OS/Arch (client): linux/amd64 Server version: 1.7.1 Server API version: 1.19 Go version (server): go1.4.2 Git commit (server): 786b29d OS/Arch (server): linux/amd64 

Nucleus:

 Linux christian-pc 4.1.0-2-amd64 #1 SMP Debian 4.1.6-1 (2015-08-23) x86_64 GNU/Linux 

mounts (excerpt):

 tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755) cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd) pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime) cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer) cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices) cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct) cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls,net_prio) cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio) cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event) cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset) systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=32,pgrp=1,timeout=0,minproto=5,maxproto=5,direct) debugfs on /sys/kernel/debug type debugfs (rw,relatime) mqueue on /dev/mqueue type mqueue (rw,relatime) hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime) /dev/sda1 on /boot type ext2 (rw,relatime) /dev/mapper/christian--pc--vg-home on /home type ext4 (rw,relatime,data=ordered) binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,relatime) tmpfs on /run/user/1000 type tmpfs (rw,nosuid,nodev,relatime,size=814904k,mode=700,uid=1000,gid=1000) fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime) gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,relatime,user_id=1000,group_id=1000) 

Any help is greatly appreciated.

+7
docker debian
source share
2 answers

I had the same problem and I found your question, as well as https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798778 , "systemd 226 init.scope breaks docker.io 1.7 0, 1 ~ dfsg1-1 ".

Due to the fact that Dmitry Smirnov says that you can add --exec-opt native.cgroupdriver=cgroupfs to DOCKER_OPTS in /etc/default/docker .

Worked for me.

+6
source share

Changing DOCKER_OPTS to use cgroupfs as in Jared Jennings answer may not be enough - as there is one more problem to check.

In a commentary on the docker question 9889, β€œzepalmer” noted that the docker systemd entry can be configured in /lib/systemd/system/docker.service not to use DOCKER_OPTS in /etc/default/docker . The consequence of this is that changing /etc/default/docker will be ineffective in how the daemon starts.

I found that this problem was true in Ubuntu 16.04.2 LTS:

Looking for /lib/systemd/system/docker.service

 [Unit] Description=Docker Application Container Engine Documentation=https://docs.docker.com After=network.target docker.socket Requires=docker.socket [Service] ExecStart=/usr/bin/docker -d -H fd:// MountFlags=slave LimitNOFILE=1048576 LimitNPROC=1048576 LimitCORE=infinity [Install] WantedBy=multi-user.target 

this is the same content as reported by zepalmer.

After changing the line "ExecStart" in the service section with the following:

 EnvironmentFile=/etc/default/docker ExecStart=/usr/bin/docker -d $DOCKER_OPTS -H fd:// 

and including --exec-opt native.cgroupdriver=cgroupfs in DOCKER_OPTS in /etc/default/docker , it seems that docker is working fine again.

+5
source share

All Articles