-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Add support for setting pids_limit in docker plugin config. #11526
Conversation
35423c9
to
0bc3d7e
Compare
0bc3d7e
to
51da191
Compare
51da191
to
d540263
Compare
139a838
to
2fbbb6f
Compare
2fbbb6f
to
7755d57
Compare
Signed-off-by: Shishir Mahajan <[email protected]>
7755d57
to
465d220
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.
Thanks @shishir-a412ed this LGTM!
I pushed a few commits to add a CHANGELOG entry and reworded the docs a bit. I also added a new test case to check if the task-level config overrides the plugin config.
I'm going to lock this pull request because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active contributions. |
Currently, Nomad doesn't have a way to enforce
pids_limit
in containers, unless set by user in their job spec.If a malicious user launches a container with a fork-bomb, that could exhaust entire nomad client host pids.
This PR will allow the operator to enforce
pids_limit
at Nomad client plugin config. User can still override thatpids_limit
in their job spec by settingpids_limit
however it must be less than the limit defined on nomad client plugin config.