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

[Michael Biebl <mbiebl@xxxxxxxxx>]

Am So., 16. Okt. 2022 um 16:23 Uhr schrieb Lennart Poettering
<lennart@xxxxxxxxxxxxxx>:
>
> On Fr, 14.10.22 22:57, Michael Biebl (mbiebl@xxxxxxxxx) 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?

No SELinux or Apparmor active

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

The host system uses systemd v241, compiled with default-hierarchy=hybrid


> Was the container configured to use either?

The container uses systemd v251 with default-hierarchy=unified

Trying to boot this container v251 container via systemd-nspawn leads to

    Welcome to Debian GNU/Linux bookworm/sid!

    Hostname set to <debian>.
    Failed to create /init.scope control group: Operation not permitted
    Failed to allocate manager object: Operation not permitted
    [!!!!!!] Failed to allocate manager object.
    Exiting PID 1...
    Container test-bookworm failed with error code 255.