Same here. Is there a quick workaround we can use before this is fixed?
I've tried to downgrade runc and docker but it didn't work.
Cheers,
Bastian
On Tue, 20 Jun 2017 14:51:02 +0200 =?UTF-8?Q?Tim_R=c3=bchsen?=
<tim.rueh...@gmx.de> wrote:
Seems to hit me on unstable since today.
runc 1.0.0~rc2+git20170201.133.9df8b30-1
systemd 233-9
container_linux.go:247: starting container process caused
"process_linux.go:359: container init caused \"rootfs_linux.go:54:
mounting \\\"cgroup\\\" to rootfs
\\\"/var/lib/docker/aufs/mnt/e9be6e7ac3cda6eee560f94f99913f636081978eb4c8fccc9d53801657e77fdb\\\"
at \\\"/sys/fs/cgroup\\\" caused \\\"no subsystem for mount\\\"\""
oci runtime error: container_linux.go:247: starting container process
caused "process_linux.go:359: container init caused
\"rootfs_linux.go:54: mounting \\\"cgroup\\\" to rootfs
\\\"/var/lib/docker/aufs/mnt/e9be6e7ac3cda6eee560f94f99913f636081978eb4c8fccc9d53801657e77fdb\\\"
at \\\"/sys/fs/cgroup\\\" caused \\\"no subsystem for mount\\\"\""
This breaks software testing here and downgrading doesn't work either.
Regards, Tim
--
Dr. Bastian Venthur http://venthur.de
Debian Developer venthur at debian org
