-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
podman run
fails with Permission denied: OCI permission denied
#14284
Comments
|
Though, I'm very curious as to how Podman can determine the node exists, but crun can't stat it - that doesn't sound like it should be possible. Potentially SELinux/Apparmor or some other security measure denying access? |
No selinux / apparmor here. Affected user belongs to |
I think podman still has access to this via the group but the oci runtime will drop all supplementary groups so it is unable to access it. |
Concur, that sounds reasonable. |
I confirm. The command:
works. |
BTW This only works with crun, not runc... |
/kind bug
Description
Podman crashes when trying to start container with --privileged.
Steps to reproduce the issue:
Running podman rootless. VirtualBox is installed on the same machine, which seems to interfere with
/dev/
contents.Run the following commands:
Describe the results you received:
Podman fails to start the container with the error above
Describe the results you expected:
The privileged container is started.
Additional information you deem important (e.g. issue happens only occasionally):
n/a
Output of
podman version
:Output of
podman info --debug
:Package info (e.g. output of
rpm -q podman
orapt list podman
):Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide? (https://github.com/containers/podman/blob/main/troubleshooting.md)
Yes
Additional environment details (AWS, VirtualBox, physical, etc.): physical, VirtualBox installed aside.
The text was updated successfully, but these errors were encountered: