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

Update part3.md (#4131)

This commit is contained in:
Wang Jie 2017-08-11 06:05:58 +08:00 committed by Misty Stanley-Jones
parent 36aadd2fe3
commit 5b44477e18
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
get-started/part3.md
View File

@ -95,7 +95,7 @@ This `docker-compose.yml` file tells Docker to do the following:
- Pull [the image we uploaded in step 2](part2.md) from the registry. - Pull [the image we uploaded in step 2](part2.md) from the registry.
- Run five instances of that image as a service - Run 5 instances of that image as a service
called `web`, limiting each one to use, at most, 10% of the CPU (across all called `web`, limiting each one to use, at most, 10% of the CPU (across all
cores), and 50MB of RAM. cores), and 50MB of RAM.
@ -146,7 +146,7 @@ Now let's run it. You have to give your app a name. Here, it is set to
docker stack deploy -c docker-compose.yml getstartedlab docker stack deploy -c docker-compose.yml getstartedlab
``` ```
See a list of the five containers you just launched: See a list of the 5 containers you just launched:
```shell ```shell
docker stack ps getstartedlab docker stack ps getstartedlab
@ -155,7 +155,7 @@ docker stack ps getstartedlab
You can run `curl http://localhost` several times in a row, or go to that URL in You can run `curl http://localhost` several times in a row, or go to that URL in
your browser and hit refresh a few times. Either way, you'll see the container your browser and hit refresh a few times. Either way, you'll see the container
ID change, demonstrating the load-balancing; with each request, one of ID change, demonstrating the load-balancing; with each request, one of
the five replicas is chosen, in a round-robin fashion, to respond. the 5 replicas is chosen, in a round-robin fashion, to respond.
>**Note**: At this stage, it may take up to 30 seconds for the containers to respond to HTTP >**Note**: At this stage, it may take up to 30 seconds for the containers to respond to HTTP