Your message dated Sat, 24 May 2014 22:17:19 +0300
with message-id
<capbrc8d3ija3h-cg9z9wuanqfsgp4jvoh4uens9xfoncxki...@mail.gmail.com>
and subject line Re: Bug#749143: docker.io: Cannot start container ... mkdir
/sys/fs/devices: operation not permitted
has caused the Debian Bug report #749143,
regarding docker.io: Cannot start container ... mkdir /sys/fs/devices:
operation not permitted
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
749143: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=749143
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: docker.io
Version: 0.11.1~dfsg1-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
When I try to run any container (eg. docker.io run busybox echo 'Hello world')
I get the message
... Error: Cannot start container ... mkdir /sys/fs/devices: operation not
permitted
Mount gives the following
--- start mount ---
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
udev on /dev type devtmpfs (rw,relatime,size=10240k,nr_inodes=749773,mode=755)
devpts on /dev/pts type devpts
(rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=601588k,mode=755)
...
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
pstore on /sys/fs/pstore type pstore (rw,relatime)
tmpfs on /run/shm type tmpfs (rw,nosuid,nodev,noexec,relatime,size=3278000k)
fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)
...
cgroup on /sys/fs/cgroup type cgroup
(rw,relatime,cpuset,cpu,cpuacct,memory,devices,freezer,net_cls,blkio,perf_event)
rpc_pipefs on /run/rpc_pipefs type rpc_pipefs (rw,relatime)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc
(rw,nosuid,nodev,noexec,relatime)
/dev/disk/by-uuid/fd3152a2-a4f0-409c-816c-453469708506 on /var/lib/docker type
ext4 (rw,relatime,errors=remount-ro,data=ordered)
systemd on /sys/fs/cgroup/systemd type cgroup
(rw,nosuid,nodev,noexec,relatime,name=systemd)
--- end mount ---
Regards
Famelis George
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.14-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=el_GR.UTF-8, LC_CTYPE=el_GR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages docker.io depends on:
ii adduser 3.113+nmu3
ii init-system-helpers 1.18
ii iptables 1.4.21-2
ii libapparmor1 2.8.0-5+b1
ii libc6 2.18-7
ii libdevmapper1.02.1 2:1.02.85-1
ii libsqlite3-0 3.8.4.3-3
ii perl 5.18.2-4
Versions of packages docker.io recommends:
ii aufs-tools 1:3.2+20130722-1.1
ii ca-certificates 20140325
ii cgroupfs-mount 1.0
ii git 1:2.0.0~rc4-1
ii xz-utils 5.1.1alpha+20120614-2
Versions of packages docker.io suggests:
ii btrfs-tools 3.14.1-1
ii debootstrap 1.0.60
ii lxc 1.0.3-1
pn rinse <none>
-- no debconf information
--- End Message ---
--- Begin Message ---
Thank you very much.
Searching the source of docker.io I had found the
contrib/check-config.sh script that
was reporting something like "cgroup hierarchy single mountpoint!" but
I didn't know that
this was so crusial.
I commented out the line about cgroup in /etc/fstab and, after
rebooting, everything is ok!!
I had added the line following instructions from
http://www.boronine.com/2013/12/30/Installing-Docker-on-Debian-Jessie/
I will inform them about the problem of single mountpoint.
Thank you very much again, Paul and Andrew
George Famelis
2014-05-24 19:01 GMT+03:00 Paul Tagliamonte <[email protected]>:
After talking with Andrew, he suggsted that this might be due to
> /sys/fs/cgroup as a single mountpoint, which is either a leftover
> from an old init script (and you just need to sudo umount /sys/fs/cgroup),
> or it's a bad entry in /etc/fstab (in which case you need to remove it or
> comment it out)
>
> (10 points to Andrew)
>
> Give that a go, see if you can confirm that's the root of the issue.
>
> Cheers,
> Paul (and Andrew, by proxy)
>
>
--- End Message ---
