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

Andreas Henriksson andreas at fatal.se
Mon Nov 7 16:01:35 GMT 2016


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




More information about the Pkg-systemd-maintainers mailing list