Public bug reported:

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??

Troubleshooting further I found there was a problem that appeared like
an issue with how systemd is setting up cgroups in the upgrade from
Focal to Jammy.

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.unified_cgroup_hierarchy=0"

Once I'd done the above and rebooted... LXD worked correctly again.

All this begs the question...
Why LXD/cgroup2 works correctly with a clean install of Ubuntu 22.04

but...
But "upgrading" a 20.04 to 22.04 causes LXD/cgroup2 to fail?

I just wanted to report this since I had multiple instances of this
occurring.

Brian

** Affects: ubuntu
     Importance: Undecided
         Status: New


** Tags: cgroup2

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971571

Title:
  ubuntu 22.04 cgroup2 works for clean install but upgrade to 22.04
  causes cgroup2 problems

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1971571/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to