Skip to content

Documenting example default-ulimit in daemon.json#1446

Merged
vdemeester merged 1 commit into
docker:masterfrom
sudo-bmitch:pr-default-ulimit
Oct 17, 2018
Merged

Documenting example default-ulimit in daemon.json#1446
vdemeester merged 1 commit into
docker:masterfrom
sudo-bmitch:pr-default-ulimit

Conversation

@sudo-bmitch

Copy link
Copy Markdown
Contributor

Signed-off-by: Brandon Mitchell git@bmitch.net

- What I did

The documentation on setting a default-ulimit using the daemon.json file was missing an example. This includes an example syntax.

(Remaining PR sections removed since this is just a documentation change.)

Signed-off-by: Brandon Mitchell <git@bmitch.net>
@codecov-io

Copy link
Copy Markdown

Codecov Report

Merging #1446 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff           @@
##           master   #1446   +/-   ##
======================================
  Coverage    54.2%   54.2%           
======================================
  Files         289     289           
  Lines       19378   19378           
======================================
  Hits        10503   10503           
  Misses       8199    8199           
  Partials      676     676

"cgroup-parent": "",
"default-ulimits": {},
"default-ulimits": {
"nofile": {

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe we can pick a different one, just because nofile is per user and not per-container.... just basically don't want someone to take this as a recommendation of some sort.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Isn't that just for nproc? I thought nofile was per process. If both are per user then we'll want to update some other docs to warn users. Might be good to have a table of each of the ulimit names and a brief description somewhere to avoid confusion.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah you are right, it is nproc!

@cpuguy83 cpuguy83 left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@vdemeester vdemeester left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM 🐯

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants