-
Notifications
You must be signed in to change notification settings - Fork 317
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
container with systemd don't start #1308
Comments
What packages did you update? podman, crun something else? It would help if you can narrow it down and share commands that you use so I can juts copy and paste in order to see if we can reproduce. |
I've tried running a container with systemd, both as root and rootless on 6.6.0-0.rc0.20230908gita48fa7efaf11.10.fc40.x86_64 with Podman 4.6.2 and crun 1.9. How was the image created? At least on Fedora, systemd is not installed at |
One way to reproduce the error is like this:
after:
or else:
the result is the same:
At the moment I don't have an older version of my operating system available, currently this is it: PLATFORM_ID="platform:f40" |
|
in Fedora 37 works.
|
@giuseppe Looks like a kernel regression maybe? I see the same symptom on the CI image update PR in different tests: https://api.cirrus-ci.com/v1/artifact/task/6621245794418688/html/int-podman-rawhide-root-host-sqlite.log.html#t--Podman-run-with-volumes-podman-run-with-mount-flag--1
Given the same works on f38 with the same crun the only logically thing is a kernel change that broke this: Could it be that crun is trying to change the permission of a symlink directly? IIRC the kernel changed the behaviour to block that. |
commit 5d1f903f75a80daa4dfb3d84e114ec8ecbf29956 in the kernel, present in a release since Linux 6.6 doesn't allow anymore to change the mode of a symlink, so just ignore the failure. Closes: containers#1308 Signed-off-by: Giuseppe Scrivano <[email protected]>
yes that is related to a change in the kernel, opened a PR: #1309 |
commit 5d1f903f75a80daa4dfb3d84e114ec8ecbf29956 in the kernel, present in a release since Linux 6.6 doesn't allow anymore to change the mode of a symlink, so just ignore the failure. Closes: containers#1308 Signed-off-by: Giuseppe Scrivano <[email protected]>
commit 5d1f903f75a80daa4dfb3d84e114ec8ecbf29956 in the kernel, present in a release since Linux 6.6 doesn't allow anymore to change the mode of a symlink, so just ignore the failure. Closes: containers#1308 Signed-off-by: Giuseppe Scrivano <[email protected]>
Alright, so after all I figured out how to resolve this with Ubuntu containers. Here's my guide for the interested: https://noobient.com/2023/11/15/fixing-ubuntu-containers-failing-to-start-with-systemd/ |
This is to workaround issues in the package shipped by the OS[1]. [1] containers/crun#1308 Closes-Bug: #2056210 Change-Id: I16f83d7e9cc127ce6997a85097d1517ce54fbefc
This is to workaround issues in the package shipped by the OS[1]. [1] containers/crun#1308 Closes-Bug: #2056210 Change-Id: I16f83d7e9cc127ce6997a85097d1517ce54fbefc
Containers get stuck in the creating state. This is a known issue[1,2] and several workarounds are suggested in the ansible-collection-kolla bug report[3]. [1] containers/crun#1308 [2] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2052961 [3] https://bugs.launchpad.net/ansible-collection-kolla/+bug/2056210 Change-Id: I16f83d7e9cc127ce6997a85097d1517ce54fbefc
Issue Description
After updating my operating system, all containers starting with /usr/bin/systemd stopped working
Steps to reproduce the issue
Steps to reproduce the issue
Describe the results you received
podman start zapzap
Describe the results you expected
start the container
podman info output
The text was updated successfully, but these errors were encountered: