Skip to content
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

Use --cap-add=NET_ADMIN instead of --privileged #10

Merged
merged 1 commit into from
Oct 7, 2014

Conversation

adrianolek
Copy link
Contributor

Ovpn doesn't need all the capabilities.
https://docs.docker.com/reference/run/#runtime-privilege-linux-capabilities-and-lxc-configuration says:

For interacting with the network stack, instead of using --privileged they should use --cap-add=NET_ADMIN to modify the network interfaces.

@kylemanna
Copy link
Owner

Hi, thanks for the patch, I like the reduced privileges.

My concern is that --cap-add was added in Docker 1.2 and many distros
(i.e. Ubuntu 14.04) are running "ancient" Docker packages
(docker.io-0.9.1~dfsg1-2) by default.

I like the reduced privileges, but want to avoid confusion for older
versions of Docker.

Could you update your patch to include both invocations and a very brief

explanation?

Ovpn doesn't need all the capabilities.
https://docs.docker.com/reference/run/#runtime-privilege-linux-capabilities-and-lxc-configuration says:
For interacting with the network stack, instead of using --privileged they should use --cap-add=NET_ADMIN to modify the network interfaces.
@adrianolek
Copy link
Contributor Author

Done

kylemanna added a commit that referenced this pull request Oct 7, 2014
Use --cap-add=NET_ADMIN instead of --privileged
@kylemanna kylemanna merged commit 543292e into kylemanna:master Oct 7, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants