systemd-nspawn uses cgroupv1
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
systemd (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Even though Ubuntu 22.04 is definitely using cgroup2:
cgroup2 on /sys/fs/
systemd appears to be using cgroup:
cgroup on /sys/fs/
cgroup on /sys/fs/
cgroup on /sys/fs/
cgroup on /sys/fs/
cgroup on /sys/fs/
cgroup on /sys/fs/
cgroup on /sys/fs/
cgroup on /sys/fs/
cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,
cgroup on /sys/fs/cgroup/rdma type cgroup (rw,nosuid,
cgroup on /sys/fs/
cgroup on /sys/fs/
cgroup on /sys/fs/cgroup/misc type cgroup (rw,nosuid,
When starting a container using default configuration from `systemd-nspawn@` unit it automatically selects cgroupv1 for some reason:
<email address hidden> - Container debian-sid
Loaded: loaded (/lib/systemd/
Active: active (running) since Sat 2024-07-20 00:48:30 +07; 1s ago
Docs: man:systemd-
Main PID: 5210 (systemd-nspawn)
Status: "Container running."
Tasks: 2 (limit: 16384)
Memory: 2.7M
CGroup: /<email address hidden>
│ └─5214 /usr/lib/
ก.ค. 20 00:48:30 ubuntu-dev systemd[1]: Starting Container debian-sid...
ก.ค. 20 00:48:30 ubuntu-dev systemd[1]: Started Container debian-sid.
ก.ค. 20 00:48:30 ubuntu-dev systemd-
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: systemd-container 249.11-0ubuntu3.12
ProcVersionSign
Uname: Linux 6.5.0-44-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckR
CurrentDesktop: ubuntu:GNOME
Date: Sat Jul 20 00:43:45 2024
InstallationDate: Installed on 2024-07-19 (0 days ago)
InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240220)
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)