From a259e68ac73210e22a8ebb77f901aecd611850e2 Mon Sep 17 00:00:00 2001 From: Muhammad Umair Khan Date: Tue, 25 Sep 2018 22:55:47 +0500 Subject: [PATCH] Correction of CPU Shares flag Flag is -c instead of --c --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 99634af..562d3e3 100644 --- a/README.md +++ b/README.md @@ -118,7 +118,7 @@ You can limit CPU, either using a percentage of all CPUs, or by using specific c For example, you can tell the [`cpu-shares`](https://docs.docker.com/engine/reference/run/#/cpu-share-constraint) setting. The setting is a bit strange -- 1024 means 100% of the CPU, so if you want the container to take 50% of all CPU cores, you should specify 512. See https://goldmann.pl/blog/2014/09/11/resource-management-in-docker/#_cpu for more: ``` -docker run -ti --c 512 agileek/cpuset-test +docker run -ti -c 512 agileek/cpuset-test ``` You can also only use some CPU cores using [`cpuset-cpus`](https://docs.docker.com/engine/reference/run/#/cpuset-constraint). See https://agileek.github.io/docker/2014/08/06/docker-cpuset/ for details and some nice videos: