FS#59973 - [systemd] systemd 239 fails to start containers with older versions of systemd
Attached to Project:
Arch Linux
Opened by Wouter Van Hemel (wvh) - Friday, 07 September 2018, 22:42 GMT
Last edited by Dave Reisner (falconindy) - Sunday, 09 August 2020, 14:38 GMT
Opened by Wouter Van Hemel (wvh) - Friday, 07 September 2018, 22:42 GMT
Last edited by Dave Reisner (falconindy) - Sunday, 09 August 2020, 14:38 GMT
|
Details
I'm starting CentOS 7.5 machines (with systemd 219) on an
Arch Linux host with systemd 239.
None of my (systemd-nspawn) machines can be started since about the update to systemd 239. The problem is with the -U (user namespace) option to systemd-nspawn: [root@arch ~]# systemctl --version systemd 239 +PAM -AUDIT -SELINUX -IMA -APPARMOR +SMACK -SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN +PCRE2 default-hierarchy=hybrid [root@arch ~]# systemd-nspawn -bUD /home/build/qbuilder/ --network-zone=machines -M qbuilder systemd.legacy_systemd_cgroup_controller=yes Spawning container builder on /home/build/qbuilder. Press ^] three times within 1s to kill container. Selected user namespace base 1649344512 and range 65536. systemd 219 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 CentOS Linux 7 (Core)! Set hostname to <qbuilder>. Failed to read AF_UNIX datagram queue length, ignoring: No such file or directory Failed to create root cgroup hierarchy: Permission denied Failed to allocate manager object: Permission denied [!!!!!!] Failed to allocate manager object, freezing. Something changed in the way systemd is handling cgroups recently and I'm not sure how to get systemd-nspawn to work again. See also: https://github.com/systemd/systemd/issues/9563 Per that thread, I'd try downgrading to systemd 238, but I don't have that package anymore. |
This task depends upon
Closed by Dave Reisner (falconindy)
Sunday, 09 August 2020, 14:38 GMT
Reason for closing: Fixed
Additional comments about closing: No response. Assume fixed as of systemd 244.
Sunday, 09 August 2020, 14:38 GMT
Reason for closing: Fixed
Additional comments about closing: No response. Assume fixed as of systemd 244.
I would suggest trying booting the host with systemd.legacy_systemd_cgroup_controller=yes instead and see if that has any effect.
It might be that systemd 219 doesn't support that parameter, but I'm not sure what patches are included in RedHat or CentOS.
Do you happen to know what changed in systemd recently that stopped this from working? Didn't version 238 also use default-hierarchy=hybrid?
You could remove the boot option and see if it was that or the kernel update that resolved the issue.
https://github.com/systemd/systemd/issues/10026