-
Notifications
You must be signed in to change notification settings - Fork 887
feat: add --net-admin
option to install script
#9953
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
Conversation
Current dependencies on/for this PR: This comment was auto-generated by Graphite. |
59e3aee
to
fcf3ea2
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we try to passively do this automatically? And then this would force failure instead?
Agree with kyle. If we could do this optimistically in the agent and avoid additional configuration that would be awesome. We could apply a similar optimistic approach to niceness. (cc @sreya) |
@kylecarbs @ammario Ideally yes, but I'd really like to learn all of the edge cases by having this opt-in for a bit. I'm using this as more of a feature flag for us to test and share with some customers. Once tested I'll make this automatic. |
For example, in Docker you can successfully add the capability to a binary. But if your container doesn't have the capability, the binary will always fail to run. There's also some security considerations when enabling this. |
fcf3ea2
to
9eb5a0e
Compare
👍🏽 |
This allows the install script to add `CAP_NET_ADMIN` to the installed binary with user consent. Combined with adding `CAP_NET_ADMIN` to the agent binary, we see an increase of >50% in networking speeds.
9eb5a0e
to
653cceb
Compare
Updates #9881 |
This allows the install script to add
CAP_NET_ADMIN
to the installedbinary with user consent. Combined with adding
CAP_NET_ADMIN
to theagent binary, we see an increase of >50% in networking speeds.