summaryrefslogtreecommitdiff
path: root/docs/source
diff options
context:
space:
mode:
authorErik Sjölund <erik.sjolund@gmail.com>2022-07-12 19:41:20 +0200
committerErik Sjölund <erik.sjolund@gmail.com>2022-07-12 19:41:20 +0200
commite83ff8e5e6fcedfd519441d42f51527126c3a7d2 (patch)
tree48b2edeee744393908c83e49ec38b8b6a197f8d2 /docs/source
parenta51a63023c773afae601628fbb89461249c5a043 (diff)
downloadpodman-e83ff8e5e6fcedfd519441d42f51527126c3a7d2.tar.gz
podman-e83ff8e5e6fcedfd519441d42f51527126c3a7d2.tar.bz2
podman-e83ff8e5e6fcedfd519441d42f51527126c3a7d2.zip
[CI:DOCS] podman-create.md: replace -c with --cpu-shares
Signed-off-by: Erik Sjölund <erik.sjolund@gmail.com>
Diffstat (limited to 'docs/source')
-rw-r--r--docs/source/markdown/podman-create.1.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/source/markdown/podman-create.1.md b/docs/source/markdown/podman-create.1.md
index 09c7d99c1..39190b501 100644
--- a/docs/source/markdown/podman-create.1.md
+++ b/docs/source/markdown/podman-create.1.md
@@ -229,8 +229,8 @@ cores. Even if a container is limited to less than 100% of CPU time, it can
use 100% of each individual CPU core.
For example, consider a system with more than three cores. If you start one
-container **{C0}** with **-c=512** running one process, and another container
-**{C1}** with **-c=1024** running two processes, this can result in the following
+container **{C0}** with **--cpu-shares=512** running one process, and another container
+**{C1}** with **--cpu-shares=1024** running two processes, this can result in the following
division of CPU shares:
PID container CPU CPU share