-
Notifications
You must be signed in to change notification settings - Fork 522
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
[docker] Add default nofiles ulimits for containers #1119
[docker] Add default nofiles ulimits for containers #1119
Conversation
4eb25b0
to
1ac5711
Compare
Move new settings to daemon.json. Re-ran the |
Can we test that the ulimit can be overridden with the |
I built an aws-ecs-1 variant image and tested with 3 different task definitions (thanks @samuelkarp for providing an example to get me started). First:
...
Next:
...
FInally:
...
This is consistent with the pre-change behavior, which is expected with such a high soft limit. |
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 Jamie!
Issue number:
#1115
Description of changes:
This change adds
--default-ulimit
to dockerd's options to set default nofiles limits for containers. The values match what are currently used by the Amazon Linux and ECS AMIs.Testing done:
Tested using the aws-dev variant
Without this change:
...
Now with the change:
...
Terms of contribution:
By submitting this pull request, I agree that this contribution is dual-licensed under the terms of both the Apache License, version 2.0, and the MIT license.