-
Notifications
You must be signed in to change notification settings - Fork 557
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
Modify the capabilities constants to match header files like other constants #160
Conversation
inside the container. Valid values are the string after `CAP_` for capabilities defined | ||
in [the man page](http://man7.org/linux/man-pages/man7/capabilities.7.html) | ||
Capabilities is an array that specifies Linux capabilities that can be provided to the process inside the container. | ||
Valid values are the strings for capabilities defined in [the man page](http://man7.org/linux/man-pages/man7/capabilities.7.html) |
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.
Maybe add (e.g. CAP_SYS_ADMIN), because those aren't strings in man.
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.
I modified the example json.
LGTM |
Why require the leading CAP_? Isn't that already clear from the
context (linux.capabilities)?
|
*.md: markdown formatting
to-may-to to-mah-to, is there a strong argument one way or the other? |
…nstants Signed-off-by: Mrunal Patel <[email protected]>
@philips Thinking it might be better to explicit in these cases and just match the values defined in the header files at the expense of typing few more characters. Rebased. |
LGTM |
lgtm |
Modify the capabilities constants to match header files like other constants
Signed-off-by: Mrunal Patel [email protected]