Guest24897
/
DockerCLI
mirror of https://github.com/docker/cli.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Added description for 'docker run' command, -c/--cpu-shares flag 

Signed-off-by: Shishir Mahajan <shishir.mahajan@redhat.com>
This commit is contained in:
shishir-a412ed 2014-11-24 16:20:18 -05:00 committed by Tibor Vass
parent 76daef2b9a
commit 41d3d7dc72
1 changed files with 13 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
docs/sources/reference/run.md
View File

@ -302,6 +302,19 @@ get the same proportion of CPU cycles, but you can tell the kernel to
give more shares of CPU time to one or more containers when you start give more shares of CPU time to one or more containers when you start
them via Docker. them via Docker.
The flag `-c` or `--cpu-shares` with value 0 indicates that the running
container has access to all 1024 (default) CPU shares. However, this value
can be modified to run a container with a different priority or different
proportion of CPU cycles.
E.g., If we start three {C0, C1, C2} containers with default values
(`-c` OR `--cpu-shares` = 0) and one {C3} with (`-c` or `--cpu-shares`=512)
then C0, C1, and C2 would have access to 100% CPU shares (1024) and C3 would
only have access to 50% CPU shares (512). In the context of a time-sliced OS
with time quantum set as 100 milliseconds, containers C0, C1, and C2 will run
for full-time quantum, and container C3 will run for half-time quantum i.e 50
milliseconds.
## Runtime privilege, Linux capabilities, and LXC configuration ## Runtime privilege, Linux capabilities, and LXC configuration
--cap-add: Add Linux capabilities --cap-add: Add Linux capabilities