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

[improvement] Please provide option to tune container's pids limit #3668

Closed
nab054371 opened this issue Dec 16, 2017 · 5 comments
Closed

[improvement] Please provide option to tune container's pids limit #3668

nab054371 opened this issue Dec 16, 2017 · 5 comments

Comments

@nab054371
Copy link

nab054371 commented Dec 16, 2017

Is it possible to please include an option to include --pids-limit option with docker driver? This is to prevent fork bomb inside the docker container. Wuold be good to please include key security options like --cap-drop=ALL and --pids-limit.

@chelseakomlo
Copy link
Contributor

Hi, thanks for the feature request. This seems like a reasonable thing to do with all supported drivers. We will review this internally.

Do you have an example of when this has been an issue? I'm curious about the context that led to this issue being opened.

@nab054371
Copy link
Author

So most organizations that are serious about docker security would prescribe the inclusion of these options when running docker containers. I have worked with several clients, where their security team has insisted on using them.

@schmichael
Copy link
Member

Crosslinking #738 as its the first mention of caps

@tgross tgross added this to Needs Roadmapping in Nomad - Community Issues Triage Feb 12, 2021
@tgross tgross removed this from Needs Roadmapping in Nomad - Community Issues Triage Mar 4, 2021
@tgross
Copy link
Member

tgross commented Oct 4, 2022

Doing some issue cleanup and this currently exists in Nomad as of #11526 which shipped in Nomad 1.2.4. It can be set on both the client and the task. See pids_limit docs.

@tgross tgross closed this as completed Oct 4, 2022
@tgross tgross added this to the 1.2.4 milestone Oct 4, 2022
@github-actions
Copy link

github-actions bot commented Feb 3, 2023

I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 3, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants