ubuntu 22.04 net_cls cgroup mounted over cgroup2 prevents LXD containers from starting
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
lxd (Ubuntu) |
Incomplete
|
Undecided
|
Unassigned |
Bug Description
I used LXD a lot.
I had 4 Ubuntu 20.04 systems I wanted to upgrade to 22.04.
Upgrading the 1st two systems (both laptops) was successful BUT .. after the upgrade I could LXD could create a new Ubuntu 22.04 or Ubuntu 20.04 container but the containers could not "start".
I spent a lot of time trying to figure out why and then gave up and just decided wipe those 2 laptops and do a "clean" install of 22.04.
The installation of 22.04 on both was successful AND.. LXD worked (ie I could create & run Ubuntu 20.04 and 22.04 containers).
The 2nd two systems were larger Desktop 20.04 systems (12 core AMD, 3-4 TB SSD, 64GB ram).
I "upgraded" 1 of those 2 Desktop systems successfully to 22.04.
However, after the upgrade, again LXD could create but NOT start Ubuntu 22.04 or 20.04 containers??
$ grep cgroup /proc/mounts**
cgroup2 /sys/fs/cgroup cgroup2 rw,nosuid,
net_cls /sys/fs/
From the above you can see that for some reason "net_cls" cgroup is being mounted over cgroup2
I found a "workaround" was to disable cgroup2 which I did by:
add the following string to the GRUB_CMDLINE_LINUX line in /etc/default/grub
and then run sudo update-grub.
"systemd.
Once I'd done the above and rebooted... LXD worked correctly again.
I just wanted to report this since I had multiple instances of this occurring.
There are also several others that have encountered this also.
Brian
affects: | ubuntu → lxd (Ubuntu) |
summary: |
- ubuntu 22.04 cgroup2 works for clean install but upgrade to 22.04 causes - cgroup2 problems + ubuntu 22.04 net_cls cgroup mounted over cgroup2 prevents LXD containers + from starting |
description: | updated |
tags: |
added: cgroup removed: bot-comment |
description: | updated |
description: | updated |
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https:/ /wiki.ubuntu. com/Bugs/ FindRightPackag e. You might also ask for help in the #ubuntu-bugs irc channel on Libera.chat.
To change the source package that this bug is filed about visit https:/ /bugs.launchpad .net/ubuntu/ +bug/1971571/ +editstatus and add the package name in the text box next to the word Package.
[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]