-
Notifications
You must be signed in to change notification settings - Fork 30
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
Docker Desktop 4.3.0+ breaks dokken images for CentOS 7 #57
Comments
Same issue confirmed here |
same with MacOS 12.0.1 and Docker Desktop 4.3.2 (72729)
UPDATE: confirmed that down grading to Docker Desktop 4.2.0 was successful as a workaround. shut down docker desktop, installed 4.2.0 and started it up, destroyed my containers and reconverged successfully. installers are here |
Facebook has a backport of systemd for centos 7, which enables cgroupv2. |
I ran into the same behavior with CentOS Stream 8 and Debian 10 images. |
@michaelklishin do get the same behavior when running the containers as described here? systemd/systemd#19760 (comment) ( |
looks pretty similar:
|
@hrak I'm sorry I meant when using centos stream 8 / debian 10. I believe you'll always need to update systemd on centos 7. |
dokken/oraclelinux-7 also broken: masdixon-mac:conmon masdixon$ docker run -it --cgroupns=host -v /sys/fs/cgroup:/sys/fs/cgroup:rw --privileged dokken/oraclelinux-7 /bin/sh |
🗣️ Foreword
Thank for taking the time to fill this bug report fully. Without it we may not be able to fix the bug, and the issue may be closed without resolution.
👻 Brief Description
Docker Desktop 4.3.0 on macOS breaks the dokken image for (at least) centos-7 as it switches to using
cgroupv2
.https://docs.docker.com/desktop/mac/release-notes/#bug-fixes-and-minor-changes
Version
Latest version of dokken/centos-7
Environment
macOS 11.6.1
Docker Desktop 4.3.1
Scenario
Attempting to use dokken/centos-7 for running a cookbook which creates a systemd service and fails verification due to systemd not running.
Steps to Reproduce
Expected Result
Process should succeed and start systemd service.
Actual Result
➕ Additional context
Add any other context about the problem here. e.g. related issues or existing pull requests.
The text was updated successfully, but these errors were encountered: