This repository was archived by the owner on Jul 2, 2023. It is now read-only.
Mark socat with CAP_NET_BIND_SERVICE capability
#3
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
|
This change shouldn't be baked into the image. It should be up to the user to add the right capabilities to their container. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Allow
socatto bind to privileged ports inside of the container when run as user process.Example command-line:
docker run --rm --user "2004" --cap-add NET_BIND_SERVICE socat tcp6-listen:443,fork tcp4:mail:443If
--cap-add NET_BIND_SERVICEis not set then this change does nothing.I guess documentation should be also updated to recommend this by default, since privilege dropping is always good.