-
Notifications
You must be signed in to change notification settings - Fork 104
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
Docker image fails: unable to set CAP_SETFCAP effective capability: Operation not permitted #355
Comments
Hello @credbbl -- apologies this isn't better documented... The upstream container image was originally used for OpenShift certification and thus required certain capabilities (like Do you want to open up a documentation change for this one? Curious to get your thoughts on where would be the best place to put it for visibility :-) Alternatively, @IohannesArnold -- do you know if removing mlock will mean we don't need this? I think this is only used for mlock and thus we can probably drop this entirely when we drop mlock in #354... but not sure if we'll end up needing this for cgroups to work or not. |
I believe this is correct. I have it removed on my local branch. |
Could you quote the part of the OpenShift certification that requires |
@credbbl I couldn't when I went looking. I wasn't directly involved in the certification effort upstream earlier (it was owned more on the partner side), but I was attempting to help clean up some of these container behaviors to be more forgiving and wasn't able to get it merged for that reasoning... I suspect either my memory is flawed or certification requirements might've changed? Not sure! As we don't have resources to pursue OpenShift certification ourselves and I've been unable to find a source requiring it, we're going to drop mlock in #363. |
Closing as #363 was merged :-) Thanks all! |
Describe the bug
The Docker image fails to start with just this message:
This is part of
/usr/local/bin/docker-entrypoint.sh
:To Reproduce
Steps to reproduce the behavior:
podman run --rm --read-only -ti quay.io/openbao/openbao:2.0.0-alpha20240329
Environment:
The text was updated successfully, but these errors were encountered: