-
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 privileged rootless podman under OpenShift SIGSEGVs #20766
Comments
Line points to Line 125 in 750b4c3
Can you run the command with |
Previously, the setup only checked for the CAP_SYS_ADMIN capability, which could be not enough with containerized Podman where CAP_SYS_ADMIN might be set for an unprivileged user. Closes: containers#20766 [NO NEW TESTS NEEDED] needs containerized Podman Signed-off-by: Giuseppe Scrivano <[email protected]>
opened a PR: #20769 This is a bit weird corner case as it requires podman to run with euid != 0 and CAP_SYS_ADMIN, which is a big hammer in this case since it applies to the host. To reproduce with Podman you need:
|
Thanks for the fix, @giuseppe. Are there some (nightly?) images somewhere where the fixed build would be available before the next release? |
you could use the copr build for each PR, e.g.: https://copr.fedorainfracloud.org/coprs/packit/containers-podman-20769/build/6691155/ |
There should be a ready to use |
Thanks! |
Previously, the setup only checked for the CAP_SYS_ADMIN capability, which could be not enough with containerized Podman where CAP_SYS_ADMIN might be set for an unprivileged user. Closes: containers#20766 [NO NEW TESTS NEEDED] needs containerized Podman Signed-off-by: Giuseppe Scrivano <[email protected]>
Previously, the setup only checked for the CAP_SYS_ADMIN capability, which could be not enough with containerized Podman where CAP_SYS_ADMIN might be set for an unprivileged user. Closes: containers#20766 [NO NEW TESTS NEEDED] needs containerized Podman Signed-off-by: Giuseppe Scrivano <[email protected]> (cherry picked from commit 41a6b99)
Issue Description
I follow https://www.redhat.com/sysadmin/podman-inside-kubernetes, running podman in an OpenShift cluster. The privileged case works fine but the
fails upon the second invocation of podman with SIGSEGV.
Steps to reproduce the issue
Steps to reproduce the issue
oc
as a regular user. Check thatoc whoami
reportsuser
.oc new-project podman-test
oc
as an admin user (user with cluster-admins group). Check thatoc whoami
reportsadmin
.oc adm policy add-scc-to-user privileged -z default -n podman-test
. We have to do this or the nextoc apply
step fails withoc
back as a regular user. Check thatoc whoami
reportsuser
.oc exec -it podman-priv -- podman info
oc exec -it podman-priv -- podman info
oc exec -it podman-rootless -- podman info
oc exec -it podman-rootless -- podman info
Describe the results you received
The
oc exec -it podman-priv -- podman info
work all the time.The
oc exec -it podman-rootless -- podman info
works the first time and the second time it printsDescribe the results you expected
No SIGSEGV, good behaviour every time.
podman info output
Podman in a container
Yes
Privileged Or Rootless
Privileged
Upstream Latest Release
Yes
Additional environment details
Additional environment details
Additional information
Additional information like issue happens only occasionally or issue happens with a particular architecture or on a particular setting
The text was updated successfully, but these errors were encountered: