-
-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ubuntu 22.04 fails to boot with read-only filesystem (Docker Desktop for macOS) #2
Comments
This seems like it's related, but I don't really understand it: https://serverfault.com/questions/1053187/systemd-fails-to-run-in-a-docker-container-when-using-cgroupv2-cgroupns-priva |
The release notes for Docker Desktop 4.3.0 include this note about using cgroup v2 (emphasis mine):
This github issue for docker desktop confirms this requirement by many users, and has lots of backlinks from other projects that use systemd that broke when Docker Desktop 4.3.0 was released. There's this comment that specifically mentions Ubuntu 22.04 requiring these options, and how the So, with regards to your docker-ubuntu2204-ansible image, I think the fix is to update README.md to include these options that are required to run it on Docker Desktop. |
This github issue for the Moby Project also confirms that it appears necessary to expose Its author offers workarounds:
Another user suggests it can also be solved using namespace isolation (--userns-remap) or by just using podman instead of docker. |
I had the same issue and I can confirm that it works with these changes... |
Did by kernel parameter:
https://docs.fedoraproject.org/en-US/fedora-coreos/kernel-args/ |
Hi Jeff,
I'm getting started with ansible and molecule, and am happy to find your pre-built images (thanks!). I'm having some trouble with the new Ubuntu 22.04 image. I'm using Docker Desktop 4.7.1 with default settings (no experimental features) on macOS 12.3.1 on a 2021 MBP w/M1 Pro.
When running docker as per the steps in README.md (except with
-it
instead of--detach
so I can see the output), it fails to boot:If I change the volume to read-write mode (by changing
--volume=/sys/fs/cgroup:/sys/fs/cgroup:ro
to--volume=/sys/fs/cgroup:/sys/fs/cgroup:rw
) it boots successfully:Is there a reason this image should be run in read-only mode, or is it safe to use in read-write mode?
Just for comparison, I also tried to boot your Ubuntu 18.04 and 20.04 images. They boot successfully in read-only mode – except for the
Failed to allocate manager object, freezing
error, do you know what is causing that?Here's geerlingguy/docker-ubuntu1804-ansible:
Here's geerlingguy/docker-ubuntu2004-ansible:
The text was updated successfully, but these errors were encountered: