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

[Michael Biebl]

What are you Missing?

Lennart Poettering <lennart at poettering.net> schrieb am So., 16. Okt. 2022,
23:45:

> On So, 16.10.22 21:02, Michael Biebl (mbiebl at gmail.com) wrote:
>
> > Am So., 16. Okt. 2022 um 16:23 Uhr schrieb Lennart Poettering
> > <lennart at poettering.net>:
> > >
> > > 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?
> >
> > 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.
>
> Please answer the questions I asked, otherwise not actionable...
>
> Lennart
>
> --
> Lennart Poettering, Berlin
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/systemd-devel/attachments/20221017/1077be97/attachment.htm>