5da38d0 breaks initialization of systemd in systemd-nspawn containers #4173
Description
Submission type
- Bug report
systemd version the issue has been seen with
git/master 5da38d0 and later
Used distribution
Gentoo (Host), Ubuntu 16.04/systemd 229 (Guest)
In case of bug report: Expected behaviour you didn't see
Booting a systemd-nspawn container using
-b/--bootwon't work anymore.
In case of bug report: Unexpected behaviour you saw
Since 5da38d0 booting a systemd-nspawn container (e.g. using Ubuntu 16.04 with systemd 229 in the container) fails:
moria ~ # systemd-nspawn -bxD /var/lib/machines/ubuntu-xenial-salt
Spawning container ubuntu-xenial-salt-2bb8317faa949977 on /var/lib/machines/.#machine.ubuntu-xenial-salt45a484ed93981a61.
Press ^] three times within 1s to kill container.
systemd 229 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN)
Detected virtualization systemd-nspawn.
Detected architecture x86-64.
Welcome to Ubuntu 16.04 LTS!
Failed to install release agent, ignoring: No such file or directory
Failed to create /init.scope control group: Read-only file system
Failed to allocate manager object: Read-only file system
[!!!!!!] Failed to allocate manager object, freezing.
Freezing execution.
In case of bug report: Steps to reproduce the problem
Install systemd 5da38d0 or later on the host
Try to start an Ubuntu 16.04 container (other OS might work as well) using the--boot/-bparam:systemd-nspawn -bxD /var/lib/machines/ubuntu-xenial-salt