-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Rootless Podman failes with "OCI permission denied" attempting to write to /proc/self/oom_score_adj on Fedora 38 #21695
Comments
I should note that other |
That is the real error you can ignore the oom_score_adj one. It usually means your binary is not executable so make sure the binary has the executable bit set. |
Ok, will dig in more to verify the script is actually runnable and come back with what I find, thanks @Luap99 . |
@Luap99 You're right, I was doing a few things wrong with my executable, this isn't a Podman problem as far as I can tell. For anyone coming here,
Sorry for the finger pointing. 😆 @Luap99 Does it make sense to add something about this to https://github.com/containers/podman/blob/main/troubleshooting.md ? By that I mean avoiding the confusion with I would be happy to contribute, if so. |
If I try this I only get
this is my output with debug:
|
Yeah, you're right @Luap99 , basically I saw the |
I mean you are more than welcome to submit a PR with some docs to describe the problem better if you think it helps others, i.e. add something to https://github.com/containers/podman/blob/main/troubleshooting.md or whatever place you looked. |
Oh, good call, I should have read the manual and checked the error code. Personally, I think that should have been enough. Will close, thanks a lot for your guidance! |
Issue Description
I'm attempting to build a
FROM scratch
container image which just copies and tries to invoke some Golang binaries, using Podman to run them. Building works fine, running produces this:Adding the
--privileged
and--group-add keep-groups
do not produce different results.I'm using the latest Podman as supplied by Fedora 38's RPMs, although admittedly Fedora is on release 39 so I might not be using what's latest-latest.
Steps to reproduce the issue
Steps to reproduce the issue
podman build
.podman run
.The Containerfile I'm using looks like this, which is somewhat contextual to the thing I'm building, but is pretty simple:
Describe the results you received
Full debug output is below:
Describe the results you expected
Podman should run the container successfully.
podman info output
Podman in a container
No
Privileged Or Rootless
Rootless
Upstream Latest Release
Yes
Additional environment details
SELinux is enforcing but not reporting any errors or violations.
Additional information
This looks very similar to #9377 and #21051 but the conclusion of those are a little unclear.
The text was updated successfully, but these errors were encountered: