Debian Bug report logs - #843509
systemd 232 breaks docker with "no subsystem for mount" error

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Jean Baptiste Favre <debian@jbfavre.org>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: systemd 232 breaks docker with "no subsystem for mount" error

Date: Mon, 07 Nov 2016 09:46:09 +0100

[Message part 1 (text/plain, inline)]

Package: systemd
Version: 231-10
Severity: important

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Dear Maintainer,

systemd upgrade to 232-x leads docker to fail with "no subsystem for mount" error.

I can't be 100% affirmative, but it could be related to new systemd-mount
installation introduced in 232-1.

Please also note that rkt is impacted, even if the error is much less clear.

- -- Package-specific info:

- -- System Information:
Debian Release: stretch/sid
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'oldstable-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.8.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages systemd depends on:
ii  adduser         3.115
ii  libacl1         2.2.52-3
ii  libapparmor1    2.10.95-5
ii  libaudit1       1:2.6.7-1
ii  libblkid1       2.28.2-1
ii  libc6           2.24-5
ii  libcap2         1:2.25-1
ii  libcryptsetup4  2:1.7.3-1
ii  libgcrypt20     1.7.3-2
ii  libgpg-error0   1.24-1
ii  libidn11        1.33-1
ii  libip4tc0       1.6.0-4
ii  libkmod2        23-1
ii  liblzma5        5.2.2-1.2
ii  libmount1       2.28.2-1
ii  libpam0g        1.1.8-3.3
ii  libseccomp2     2.3.1-2
ii  libselinux1     2.6-1
pn  libsystemd0     <none>
ii  mount           2.28.2-1
ii  util-linux      2.28.2-1

Versions of packages systemd recommends:
ii  dbus            1.10.12-1
pn  libpam-systemd  <none>

Versions of packages systemd suggests:
ii  policykit-1        0.105-17
pn  systemd-container  <none>
pn  systemd-ui         <none>

Versions of packages systemd is related to:
pn  dracut           <none>
ii  initramfs-tools  0.125
ii  udev             232-2

- -- no debconf information

-----BEGIN PGP SIGNATURE-----

iQJ8BAEBCgBmBQJYID9FXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ0RTg0NUJBMjMwQ0I0RDQ0ODkwNjk4NDdC
NERENTM2QUNGN0Q4NzM3AAoJELTdU2rPfYc3uu0QAJLuWpPSx6NLDMNteuYTPy4A
14NH7nyClK/ipUQB/+y0cH13lB0i2rM5Z6pwBCa0utAUmIxEeTaenuN9qxiP6hsF
21nFmaTRMl187d0SjhU4R1u0m5eb9HKrn/eYX8/TnqDppUKJZTLCqHLqCmwELKpt
FRiHRbzrXWS0xl94fO6bAIyz8QuCuQoGUWujsMZUF74OZb5IL17gUy08xDW7cjil
c0DQ83LO/e68CK4jRN/QQ2miqomYCZ2/AePpOegAj2FagBAS7f4a+6GIeeWOWEmb
R+2kNmw/Bw2Jq2o+Tgd1eyGF94BqSMRs9sewdZ3XkpMyUZ3tCyAlSyudBHguN4lm
B92Kq/gpToKMUzgGDREeW5H1k9rrSZ1vwEYTcc7zGiOb4YpYSk7bdrsw+r2TLokL
2gq9SDpCinyTEyMKBnOcgCuwCrWakqn+GiLIzKqAv2heffW5kCs/FWATfXS8yDR4
Bv4ojrFL0rgVEJmno2ayIVUr0DIFNGs0bMPGqYSsfD3VPsxu0HLEanRMIDJ0dA3x
23+arUI1dCm1B0aeaFU6RNot3zXVabW+m3ztIIALJVPFnz8KZ1th3J8dZS9/vDlD
mt93qHRRXtEKj0lwGErflXDO24/yp/sCoglBM99Kvf9Uwons/2PL/+exaL8JgHow
PEKsyiuh/SwesqykCSJg
=Ra2O
-----END PGP SIGNATURE-----

[systemd-delta.txt (text/plain, attachment)]

[systemd-analyze-dump.txt (text/plain, attachment)]

[dsh-enabled.txt (text/plain, attachment)]

[fstab (text/plain, attachment)]

Message #16 received at 843509@bugs.debian.org (full text, mbox, reply):

From: Felipe Sateler <fsateler@debian.org>

To: Jean Baptiste Favre <debian@jbfavre.org>, 843509@bugs.debian.org

Subject: Re: Bug#843509: systemd 232 breaks docker with "no subsystem for mount" error

Date: Mon, 7 Nov 2016 09:49:25 -0300

Control: tags -1 moreinfo

On 7 November 2016 at 05:46, Jean Baptiste Favre <debian@jbfavre.org> wrote:
> Package: systemd
> Version: 231-10
> Severity: important
>
> Hash: SHA512
>
> Dear Maintainer,
>
> systemd upgrade to 232-x leads docker to fail with "no subsystem for mount" error.
>
> I can't be 100% affirmative, but it could be related to new systemd-mount
> installation introduced in 232-1.
>
> Please also note that rkt is impacted, even if the error is much less clear.

Is the issue fixed if you boot with
systemd.legacy_systemd_cgroup_controller=1 boot parameter?

-- 

Saludos,
Felipe Sateler

Message #23 received at 843509@bugs.debian.org (full text, mbox, reply):

From: Jean Baptiste Favre <debian@jbfavre.org>

To: 843509@bugs.debian.org

Cc: Felipe Sateler <fsateler@debian.org>

Subject: Re: Bug#843509: systemd 232 breaks docker with "no subsystem for mount" error

Date: Mon, 7 Nov 2016 15:53:34 +0100

[Message part 1 (text/plain, inline)]

On 07/11/2016 13:49, Felipe Sateler wrote:
> Control: tags -1 moreinfo
> 
> On 7 November 2016 at 05:46, Jean Baptiste Favre <debian@jbfavre.org> wrote:
>> Package: systemd
>> Version: 231-10
>> Severity: important
>>
>> Hash: SHA512
>>
>> Dear Maintainer,
>>
>> systemd upgrade to 232-x leads docker to fail with "no subsystem for mount" error.
>>
>> I can't be 100% affirmative, but it could be related to new systemd-mount
>> installation introduced in 232-1.
>>
>> Please also note that rkt is impacted, even if the error is much less clear.
> 
> Is the issue fixed if you boot with
> systemd.legacy_systemd_cgroup_controller=1 boot parameter?
> 

Hello,
Provided workaround works for docker.
rkt still fails with following message:

sudo rkt run --debug=true --interactive quay.io/coreos/alpine-sh
image: using image from file /usr/lib/rkt/stage1-host.aci
image: using image from local store for image name quay.io/coreos/alpine-sh
stage0: Preparing stage1
stage0: Writing image manifest
stage0: Loading image
sha512-2222d0a867084bc1c6f47f86982867dcc013a1bcfab15128a1065108808fc998
stage0: Writing image manifest
stage0: Writing pod manifest
stage0: Setting up stage1
stage0: Wrote filesystem to
/home/rkt/pods/run/b7bb62f1-5045-49df-b59a-226341ac9cb4
stage0: Pivoting to filesystem
/home/rkt/pods/run/b7bb62f1-5045-49df-b59a-226341ac9cb4
stage0: Execing
[/home/rkt/pods/run/b7bb62f1-5045-49df-b59a-226341ac9cb4/stage1/rootfs/init
--debug --net=default --interactive --local-config=/etc/rkt
b7bb62f1-5045-49df-b59a-226341ac9cb4]
networking: loading networks from /etc/rkt/net.d
networking: loading network default with type ptp
stage1:
  └─unable to probe /usr/bin/systemd-nspawn version
    └─exit status 1

Not sure it's the same issue though

Regards,
Jean Baptiste Favre

[signature.asc (application/pgp-signature, attachment)]

Message #28 received at 843509@bugs.debian.org (full text, mbox, reply):

From: Andreas Henriksson <andreas@fatal.se>

To: Jean Baptiste Favre <debian@jbfavre.org>

Cc: 843509@bugs.debian.org, Felipe Sateler <fsateler@debian.org>

Subject: Re: Bug#843509: systemd 232 breaks docker with "no subsystem for mount" error

Date: Mon, 7 Nov 2016 17:01:35 +0100

On Mon, Nov 07, 2016 at 03:53:34PM +0100, Jean Baptiste Favre wrote:
[...]
> networking: loading networks from /etc/rkt/net.d
> networking: loading network default with type ptp
> stage1:
>   └─unable to probe /usr/bin/systemd-nspawn version
>     └─exit status 1
> 
> Not sure it's the same issue though

This seems like a separate issue which likely deserves its own bug report:

$ systemd-nspawn --version ; echo $?
systemd 231
+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN
0


# systemd-nspawn --version ; echo $?
systemd 232
+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN
1


http://sources.debian.net/src/rkt/1.5.0%2Bdfsg-1/stage1/init/init.go/#L350

Regards,
Andreas Henriksson

Message #33 received at 843509@bugs.debian.org (full text, mbox, reply):

From: Jean Baptiste Favre <debian@jbfavre.org>

To: 843509@bugs.debian.org, control@bugs.debian.org

Cc: Andreas Henriksson <andreas@fatal.se>

Subject: Re: Bug#843509: systemd 232 breaks docker with "no subsystem for mount" error

Date: Mon, 7 Nov 2016 17:04:54 +0100

[Message part 1 (text/plain, inline)]

affects 843509 - rkt
thanks

On 07/11/2016 17:01, Andreas Henriksson wrote:
> On Mon, Nov 07, 2016 at 03:53:34PM +0100, Jean Baptiste Favre wrote:
> [...]
>> networking: loading networks from /etc/rkt/net.d
>> networking: loading network default with type ptp
>> stage1:
>>   └─unable to probe /usr/bin/systemd-nspawn version
>>     └─exit status 1
>>
>> Not sure it's the same issue though
> 
> This seems like a separate issue which likely deserves its own bug report:
> 
> $ systemd-nspawn --version ; echo $?
> systemd 231
> +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN
> 0
> 
> 
> # systemd-nspawn --version ; echo $?
> systemd 232
> +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN
> 1
> 
> 
> http://sources.debian.net/src/rkt/1.5.0%2Bdfsg-1/stage1/init/init.go/#L350
> 
> Regards,
> Andreas Henriksson
> 

Didn't thought about echo $? :-/

Will remove the affect part from rkt and open a separate bug.
Guess it'll be against systemd as well since the exit code of
systemd-nspawn seems to be wrong in 232.

Regards,
Jean Baptiste

[signature.asc (application/pgp-signature, attachment)]

Message #40 received at 843509-close@bugs.debian.org (full text, mbox, reply):

From: Martin Pitt <mpitt@debian.org>

To: 843509-close@bugs.debian.org

Subject: Bug#843509: fixed in systemd 232-3

Date: Wed, 09 Nov 2016 09:33:57 +0000

Source: systemd
Source-Version: 232-3

We believe that the bug you reported is fixed in the latest version of
systemd, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 843509@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Martin Pitt <mpitt@debian.org> (supplier of updated systemd package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Wed, 09 Nov 2016 09:34:45 +0100
Source: systemd
Binary: systemd systemd-sysv systemd-container systemd-journal-remote systemd-coredump libpam-systemd libnss-myhostname libnss-mymachines libnss-resolve libsystemd0 libsystemd-dev udev libudev1 libudev-dev udev-udeb libudev1-udeb
Architecture: source
Version: 232-3
Distribution: unstable
Urgency: medium
Maintainer: Debian systemd Maintainers <pkg-systemd-maintainers@lists.alioth.debian.org>
Changed-By: Martin Pitt <mpitt@debian.org>
Description:
 libnss-myhostname - nss module providing fallback resolution for the current hostname
 libnss-mymachines - nss module to resolve hostnames for local container instances
 libnss-resolve - nss module to resolve names via systemd-resolved
 libpam-systemd - system and service manager - PAM module
 libsystemd-dev - systemd utility library - development files
 libsystemd0 - systemd utility library
 libudev-dev - libudev development files
 libudev1   - libudev shared library
 libudev1-udeb - libudev shared library (udeb)
 systemd    - system and service manager
 systemd-container - systemd container/nspawn tools
 systemd-coredump - tools for storing and retrieving coredumps
 systemd-journal-remote - tools for sending and receiving remote journal logs
 systemd-sysv - system and service manager - SysV links
 udev       - /dev/ and hotplug management daemon
 udev-udeb  - /dev/ and hotplug management daemon (udeb)
Closes: 843070 843433 843509 843544
Changes:
 systemd (232-3) unstable; urgency=medium
 .
   [ Felipe Sateler ]
   * Make systemd-delta less confused on merged-usr systems. (Closes: #843070)
   * Fix wrong paths for /bin/mount when compiled on merged-usr system.
     Then the build system finds /usr/bin/mount which won't exist on a
     split-/usr system. Set the paths explicitly in debian/rules and drop
     Use-different-default-paths-for-various-binaries.patch. (Closes: #843433)
 .
   [ Martin Pitt ]
   * debian/tests/logind: Split out "pid in logind session" test
   * debian/tests/logind: Adjust "in logind session" test for unified cgroup
     hierarchy
   * debian/tests/boot-and-services: Check common properties of CLI programs.
     Verify that CLI programs have a sane behaviour and exit code when being
     called with --help, --version, or an invalid option.
   * nspawn: Fix exit code for --help and --version (Closes: #843544)
   * core: Revert using the unified hierarchy for the systemd cgroup.
     Too many things don't get along with it yet, like docker, LXC, or runc.
     (Closes: #843509)
Checksums-Sha1:
 7b8cde16d2549bca1710c2de2a036acd8c2e12cb 4481 systemd_232-3.dsc
 85cdd2f2a097894a70a19106b175524a3c2c2336 125844 systemd_232-3.debian.tar.xz
Checksums-Sha256:
 86ff25eba735ef1dc85221d61520f8e9703946cc78379116e37b501081eef0c5 4481 systemd_232-3.dsc
 e4e82bfd87cfc9b28303e58f88cca4ea3c8a3d51fbc403ecdf3698fb10a8a6dc 125844 systemd_232-3.debian.tar.xz
Files:
 25d3be1d19bc533b29b9cef6bbce956e 4481 admin optional systemd_232-3.dsc
 25825e4d6999b689c0ac7cc2114009ed 125844 admin optional systemd_232-3.debian.tar.xz

-----BEGIN PGP SIGNATURE-----

iQIcBAEBCAAGBQJYIupvAAoJENFO8V2v4RNHrrcQAKJwJ/qFjEuqnqeDQpf25xdp
9kbWL8NhwaKWbjPLCLTUqZk8rNZGZT6+n7VWPIkZMiBuCK+pkLTLJm/+1gwZQxAC
+FSDgj+a9XRurfMt1TRLg65w/XZJ3orU3FGzjhuozqW7AZVqsdCWhQ4qbLCbwm10
Fow1ZPfPMHYA4uCJTNopNputek/+KUgdA40cQ5qtC2PnK/uVnulleYwR6HAJUmnw
xk8NV6iul6aCVAGYSBNZHZltSgyvunbg/wwinHbjMN/k09vh5ZYtUr63fgq7Nq+m
tgysWMRdCchVrtUMVJTwSzZgiaYG2wrhguCQ/B/CD5CG/cNiv4NwnF+ComHDprGK
GhEmcg4e1Le0U0bcpAfOxLIkxc6e2t5PMIKf7tWHtFmtIalHwNMg13gYKaDWa/gw
rnjxKRcmKPaRLoqT8/AJGGr4iCfx9uO2LnTJsDRpJUeZWulqoMQASKIWetYfk6iw
quyUT+KT6RHyjV39iRjAPprT5i4VQaTWZvYJ29oMPbLguS7Wz/FZ6xLdiYWmsWlP
b5egMhcbL4wMI+4HtS5LfPw4X9roDPVzzyMipvTLb/RZKUuV5tKuyGXdGH6EcYXM
sHQtqEUodbIcLoA0lt0gH9QrONFg6/9lH7mQIMepHvrX26EcCp3++tXuyoHaH/GH
YAfTDFZMLr2H+nmTf0jU
=ogq1
-----END PGP SIGNATURE-----

Send a report that this bug log contains spam.