Ubuntu 23.10 (mantic) containers fail to start #788
Labels
Incomplete
Waiting on more information from reporter
Comments
|
Added a line: to the config file, but it still gives the same error. Next up is attempting to convince systemd to print more information... |
|
Also suffer from this issue. |
|
I'm not having any problem here, what kernel are you using? |
|
In my case, it is with an Ubuntu 22.04 LTS host, using the Another note is that I am using |
|
Please try on a system without And yes, that effectively means that you'll have to chose between having your system being able to run older distros (Ubuntu 18.04, CentOS 7, ...) and being able to run modern distros as older ones don't understand cgroup2 and newer ones no longer understand cgroup1. |
|
No special boot options in my case. Host os is |
|
Ubuntu 20.04 defaults to cgroup1 so you'd need to pass a boot parameter to force cgroup2 or upgrade your system to 22.04 |
|
Same with 22.04 machine: |
|
@unxed can you show:
|
|
For sure! |
|
Can you show the output of |
|
|
Ah, right so you're hitting: This is something that's been fixed in lxc/lxc#4295 but hasn't been part of an LXC release yet as we're waiting on the various distros to catch the newer apparmor first. If your system has apparmor 2.13.8 or 3.0.10 (and newer), then you could try applying the changes directly to your files in /etc/apparmor.d, reboot the system and try again: That should take care of the DENIED that you're seeing in dmesg and hopefully let systemd boot properly. This whole mess came from a bad security bug in apparmor which apparmor upstream pretty much ignored for a decade until @mihalicyn decided to just go and fix it for them earlier this year. |
|
This helped, thank you! Works both on 20.04 and 22.04 Had to update and then |
|
Closing as there's nothing we can really do with the image, things will improve as distros update their apparmor and liblxc. |
|
Here on Ubuntu 22.04 this also worked around the problem, but as the apparmor version seems to be Especially since @stgraber mentions:
which is unfortunately not the case on Ubuntu 22.04. But I don't get any complaints from |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Starting a freshly created mantic (20231014_07:42) container results in:
This looks very much like systemd/systemd#27436, so it might indeed be due to some issue with
/tmpnot being available in the initial file system. I will check if I can work around it with a custom config file.The text was updated successfully, but these errors were encountered: