-
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
Error: readlink: Permission denied: OCI permission denied #10912
Comments
A friendly reminder that this issue had no activity for 30 days. |
Podman top [It] podman pod top on pod with containers in same pid namespace
Podman pod create [It] podman pod container can override pod not sharing pid
Podman pod create [It] podman pod correctly sets up PIDNS
|
A friendly reminder that this issue had no activity for 30 days. |
I've been keeping flake logs for a few months, and on August 17 I wrote a tool to grep those logs. The last occurrence of "readlink" on the same line as "Permission denied" was August 10 (already logged in comment above). It's possible that the error message changed, also possible that the issue magically fixed itself. I don't think there's anything I can do aside from close the issue. |
Reopening: this is still happening. Podman pod create [It] podman pod create with --userns=keep-id can add users
Podman pod create [It] podman pod create with --userns=auto
Podman pod create [It] podman pod create with --userns=keep-id
Podman pod create [It] podman pod create --userns=auto:size=%d
Two observations:
|
@giuseppe, could this be a crun issue? |
No you are running a container within a Pod and already have set the userns size to 500, now you are attempting to set a container in the same user namesapce to use 3000 uids, which is not allowed. What should happen here is --pod and userns option should conflict if container is sharing userns with the pod. |
BTW We should do that for all of the namespace options. If you share a namespace with the pod, then you should use the options set within the pod. |
593d090 just did this for conflicting --hostname when in a Pod. |
A friendly reminder that this issue had no activity for 30 days. |
Looks like current code at least conflicts setting USERNS within a Pod that is using user namespace. Not sure if this is enough to close down this issue. |
Most recent instance was Jan 12: [sys] 236 podman selinux: shared context in (some) namespaces
That instance does not seem to have anything to do with userns or pods:
|
A friendly reminder that this issue had no activity for 30 days. |
A friendly reminder that this issue had no activity for 30 days. |
Nothing in my logs since Jan 12; make of that what you will. |
3 Months, Time to close... |
A friendly reminder that this issue had no activity for 30 days. |
@edsantiago Close? |
No new instances since Jan 12. Okay, closing. |
Seen today in f37 rootless. Reopening.
|
@giuseppe could this be a race in |
@edsantiago waiting for response from you |
No instances since the one on May 1 |
This is one of those flakes that appear at random, in random tests, making it almost impossible for my flake-logger to isolate. Symptom is:
One interesting thing: I see this (sometimes, not always) with
run -d
, implying that the error happens before detach.Podman UserNS support [It] podman --userns=container:CTR
Podman pod create [It] podman pod container can override pod not sharing pid
Podman run [It] podman shared PID NS container share SELinux labels
Podman pod create [It] podman pod correctly sets up PIDNS
Podman top [It] podman pod top on pod with containers in same pid namespace
sys: podman selinux: shared context in (some) namespaces
The text was updated successfully, but these errors were encountered: