Public bug reported:
[impact]
after systemd was changed to default to cgroupv2, any container started
on a host that still uses legacy or hybrid cgroup mounts will result in
a container that attempts to use unified cgroup but can't due to all the
controllers being used as v1 in the host kernel.
[test case]
TBD
[regression potential]
container, or vm or bare metal, that incorrectly uses cgroupv1, or
incorrect use of cgroupv2.
[scope]
needed only for i and later
f and earlier default to cgroupv1
** Affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Affects: systemd (Ubuntu Impish)
Importance: Undecided
Status: New
** Affects: systemd (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Impish)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1950508
Title:
unified cgroup incorrectly used in container on host with
legacy/hybrid cgroup
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1950508/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
