-
-
Notifications
You must be signed in to change notification settings - Fork 68
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
Trying to run heplify as non-root, with cap_add in a container #273
Comments
It seems the binary will need |
@TheQue42 absolutely, feel free to open a PR with the proposed changes and we'll go from there |
I'd love to, but since the "RUN setcap" command cant be run in the "FROM scratch" image you use now, we'd have to change the empty base image into a "real" image that contains setcap. And I am not sure I am the one to decide which you want? |
heplify will run fine in any image, the scratch choice was purely related to size and proving the static build. |
Seems like this works. https://github.com/TheQue42/heplify/blob/master/docker/heplify/Dockerfile I'll continue tomorrow :-) |
It looks promising! let us know if you notice any other issues before we make this the new standard |
Super! My docker-compose with:
Will now work fine! |
Hi,
My attempts at running heplify in a non-root docker container, adding capabilities with:
in docker-compose.
But I just get:
Critical: setting af_packet handle: operation not permitted
Any pointers?
The text was updated successfully, but these errors were encountered: