summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorErik Sjölund <erik.sjolund@gmail.com>2022-07-12 19:41:20 +0200
committerMatthew Heon <matthew.heon@pm.me>2022-07-26 13:09:02 -0400
commit5f5379deb5520d75f747467c3076919f0297b4bc (patch)
tree3dc5873e7b315366b9e9b879e55202f89cafe2a6
parentf7707c81a0ff91364541f3be600a970fd1b59476 (diff)
downloadpodman-5f5379deb5520d75f747467c3076919f0297b4bc.tar.gz
podman-5f5379deb5520d75f747467c3076919f0297b4bc.tar.bz2
podman-5f5379deb5520d75f747467c3076919f0297b4bc.zip
[CI:DOCS] podman-create.md: replace -c with --cpu-shares
Signed-off-by: Erik Sjölund <erik.sjolund@gmail.com>
-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 e7faeb820..50a90b9ba 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