Merge pull request wsargent#167 from xsoh/patch-1

Replace `-ti` with `-it` to unify it in the Readme
asleekgeek · Mar 18, 2019 · f60a256 · f60a256
2 parents 509c3d6 + c458d5d
commit f60a256
Showing 1 changed file with 3 additions and 3 deletions.
diff --git a/README.md b/README.md
@@ -142,13 +142,13 @@ 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 -it -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:
 
 ```
-docker run -ti --cpuset-cpus=0,4,6 agileek/cpuset-test
+docker run -it --cpuset-cpus=0,4,6 agileek/cpuset-test
 ```
 
 Note that Docker can still **see** all of the CPUs inside the container -- it just isn't using all of them.  See <https://github.com/docker/docker/issues/20770> for more details.
@@ -818,7 +818,7 @@ docker run --rm httpd cat /usr/local/apache2/conf/httpd.conf > httpd.conf
 vim httpd.conf
 
 # start container with modified configuration
-docker run --rm -ti -v "$PWD/httpd.conf:/usr/local/apache2/conf/httpd.conf:ro" -p "80:80" httpd
+docker run --rm -it -v "$PWD/httpd.conf:/usr/local/apache2/conf/httpd.conf:ro" -p "80:80" httpd
 ```
 
 ## Contributing