-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Second invocation of podman info
in rootless container SIGSEGVs
#20908
Comments
@umohnani8 mind poking this one? iirc, you did work on podman in podman |
Seems to be hitting a capabilty. $ /bin/podman run --cap-add=sys_admin -ti --rm quay.io/podman/stable sh -c "podman info; podman info" Works for me, where it blows up without the CAP_SYS_ADMIN |
@giuseppe I am thinking this has something to do with setting up a podman usernamespace? Basically the first podman command works, but the second fails, which to me indicates that the second podman is attempting to enter the user namespace. If I add CAP_SYS_ADMIN then it does not use the user namesspace on the second call. |
I could be wrong, I went into the container ran the podman info and it left a This is definitely something about running podman with CAP_SYS_ADMIN capabilty. |
is it a duplicate of #20766 ? |
No, that one was about This one is about no capabilities in that rootless container. |
opened a PR: #21017 marked as draft for now as I want to test it better before it is ready for review |
it is the wrong check to do here since we need to setup the user namespace even in the case we are running as root without capabilities. [NO NEW TESTS NEEDED] this happens in nested podman Closes: containers#20908 Signed-off-by: Giuseppe Scrivano <[email protected]>
it is the wrong check to do here since we need to setup the user namespace even in the case we are running as root without capabilities. [NO NEW TESTS NEEDED] this happens in nested podman Closes: containers#20908 Signed-off-by: Giuseppe Scrivano <[email protected]> (cherry picked from commit 1322f31)
Issue Description
Running
podman info
in a rootless unprivileged container leads to SIGSEV.Steps to reproduce the issue
Steps to reproduce the issue
$ podman run -ti --rm quay.io/podman/stable sh -c 'podman info; podman info'
Describe the results you received
Describe the results you expected
Two
podman info
outputs, not traceback.podman info output
Output of
podman info
in the container is shown above.podman info
on the host:Podman in a container
Yes
Privileged Or Rootless
Rootless
Upstream Latest Release
Yes
Additional environment details
Reproduced on fresh Fedora 39 installation.
Additional information
Deterministic.
Reproduced with
quay.io/podman/upstream
as well.Possibly related / continuation of #20766.
The text was updated successfully, but these errors were encountered: