Bug#943981: Proposal: Switch to cgroupv2 by default

Michael Biebl biebl at debian.org
Thu Apr 23 11:52:48 BST 2020

Am 23.04.2020 um 06:04 schrieb Ryutaroh Matsumoto:
> Hi Michael,
> I filed two unwelcome interactions between systemd and LXC on Debian:
> (1) lxc: jessie LXC container does not start on hosts with cgroup2 / unified hierarchy
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958507

Hm, I probably wouldn't worry too much. Jessie is already really old and
bullseye (for which the change is targetted) will not be released for
yet another year.
Then again, I don't know if it's an important use-case for admins to be
able to run jessie containers on a bullseye host.

> (2) lxc: autopkgtest of systemd in stretch fails with LXC backend in cgroup2 / unified hierarchy
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958508

The networkd test is flaky sometimes. I've seen it fail occasionally.
Can you reliably reproduce the failure with this setup?


P.S.: Thanks for your ongoing efforts regarding the cgroupv2 switch.
This is very much appreciated.
What are your thoughts regarding doing the switch? Are we there yet
(once lxc v4 enters testing)? For me lxc is the main blocker and we
probably can't wait for docker (I would document that in the release
notes / NEWS entry instead what docker users can do)

Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20200423/72b3eef1/attachment.sig>

More information about the Pkg-systemd-maintainers mailing list