[systemd-devel] systemd-container: Trying to use a bookworm chroot with a buster host fails / Failed to create /init.scope control group

Lennart Poettering lennart at poettering.net
Sun Oct 16 14:23:46 UTC 2022


On Fr, 14.10.22 22:57, Michael Biebl (mbiebl at gmail.com) wrote:

> Hi,
>
> since the issue came up on the Debian bug tracker at
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019147 , I figured
> I ask here:

Do you have any MACs in effect?

Does the host use cgroupsv2 or cgroupsv2 or hybrid? What is mounted to
/sys/fs/cgroup and below?

Was the container configured to use either?

This is new payload on old host?

if you force container into cgroupsv1 mode as the host (by adding
systemd.unified_cgroup_hierarchy=no to the nspawn cmdline, does that
work?

Generally, systemd should discover everything on its own and just work
when run in an older container manager/cgroup environment. But it's
not something we would regularly test.

Lennart

--
Lennart Poettering, Berlin


More information about the systemd-devel mailing list