Arch Linux

h0tbird

Member

Registered: 2013-05-21

Posts: 8

Docker fails with "no subsystem for mount"

Docker fails:

[0] ~ >> docker run -it --rm alpine:3.5 /bin/sh
docker: Error response from daemon: 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/devicemapper/mnt/515b55ad13ea6be27f2c09201f5328b15175421a11dee081a85ab30294fdfffb/rootfs\\\" at \\\"/sys/fs/cgroup\\\" caused \\\"no subsystem for mount\\\"\"".

Docker version:

[0] ~ >> docker version
Client:
 Version:      17.03.0-ce
 API version:  1.26
 Go version:   go1.8
 Git commit:   60ccb2265b
 Built:        Sun Mar  5 13:38:03 2017
 OS/Arch:      linux/amd64

Server:
 Version:      17.03.0-ce
 API version:  1.26 (minimum version 1.12)
 Go version:   go1.8
 Git commit:   60ccb2265b
 Built:        Sun Mar  5 13:38:03 2017
 OS/Arch:      linux/amd64
 Experimental: false

Kernel version:

[0] ~ >> uname -a                              
Linux arch 4.10.2-1-ARCH #1 SMP PREEMPT Mon Mar 13 17:13:41 CET 2017 x86_64 GNU/Linux

Systemd version:

[0] ~ >> pacman -Q systemd                     
systemd 233-1

Related to Red Hat Bugzilla – Bug 1411286

Last edited by h0tbird (2017-03-15 12:29:05)

Awebb

Member

Registered: 2010-05-06

Posts: 6,286

Re: Docker fails with "no subsystem for mount"

Just so this doesn't go wrong: Is this for our information - in which case: thank you! - or is this a request for help in fixing the problem, in which case we'd need more information, like how you installed docker, a link to a sample image not working, etc.

h0tbird

Member

Registered: 2013-05-21

Posts: 8

Re: Docker fails with "no subsystem for mount"

Just so this doesn't go wrong: Is this for our information - in which case: thank you! - or is this a request for help in fixing the problem, in which case we'd need more information, like how you installed docker, a link to a sample image not working, etc.

It is both a FYI and also a request for help. I also want to know if I am the only Arch user with this problem and I am interested in fixes and workarounds. I installed Docker using pacman and I am quite sure that any docker image I try will fail to start.

Docker package:

[0] ~ >> pacman -Qii docker
Name            : docker
Version         : 1:17.03.0-1
Description     : Pack, ship and run any application as a lightweight container
Architecture    : x86_64
URL             : https://www.docker.com/
Licenses        : Apache
Groups          : None
Provides        : None
Depends On      : bridge-utils  iproute2  device-mapper  sqlite  systemd  libseccomp
Optional Deps   : btrfs-progs: btrfs backend support
                  lxc: lxc backend support
Required By     : None
Optional For    : None
Conflicts With  : None
Replaces        : None
Installed Size  : 84.77 MiB
Packager        : Sébastien Luttringer <seblu@seblu.net>
Build Date      : Sun 05 Mar 2017 01:39:12 PM CET
Install Date    : Mon 06 Mar 2017 10:07:33 AM CET
Install Reason  : Explicitly installed
Install Script  : No
Validated By    : Signature
Backup Files    :
(none)

Thank you Awebb!

Last edited by h0tbird (2017-03-15 12:34:57)

Awebb

Member

Registered: 2010-05-06

Posts: 6,286

Re: Docker fails with "no subsystem for mount"

I faintly remember reading something about this being a problem with a new... err... unified cgroup handling in systemd 232. I think (or guess I assume I think :-O) this is related to this one: https://github.com/systemd/systemd/pull/4670 and https://github.com/docker/docker/issues/28109.

The whole thing makes me want to postpone that reboot after the recent update.

EDIT: However, I don't get the error for the base/archlinux image (ran with sudo docker run -it --rm base/archlinux /bin/bash), the only image I use. I just updated the entire system and rebooted. I cannot reproduce your error.

Last edited by Awebb (2017-03-15 12:54:54)

Awebb

Member

Registered: 2010-05-06

Posts: 6,286

Re: Docker fails with "no subsystem for mount"

Well, what is this? 233-1 isn't in core yet, core still has 232-8. You're running [testing]. Next time please mention [testing] and post in the testing sub forum. I'm still glad this caught my eye. Maybe you want to chime in on the mailing list, and/or report a bug against the package in Testing (https://www.archlinux.org/packages/test … 4/systemd/), so it doesn't go live by accident until the issue is fixed.

h0tbird

Member

Registered: 2013-05-21

Posts: 8

Re: Docker fails with "no subsystem for mount"

Oh! thank you for pointing that out. I don't even remember when I enabled testing.
After downgrading to 232-8 it started to work again.

Thanks again Awebb!

Awebb

Member

Registered: 2010-05-06

Posts: 6,286

Re: Docker fails with "no subsystem for mount"

Have you, you know... opened a bug report against systemd in testing, so we don't end up having to manually mount the cgroups every time? I would, but I don't feel comfortable reporting a bug I can't reproduce on my system and I don't have a test box at hand. You can drop the link to the report here and I add whatever I found. You find a "bug report" link on the package page I gave you in the last post.

h0tbird

Member

Registered: 2013-05-21

Posts: 8

Re: Docker fails with "no subsystem for mount"

Here you have it: https://bugs.archlinux.org/task/53327?p … ened=25103

h0tbird

Member

Registered: 2013-05-21

Posts: 8

Re: Docker fails with "no subsystem for mount"

... which happens to be a duplicated of https://bugs.archlinux.org/task/53271