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

updates per feedback (#4836) 

Signed-off-by: Victoria Bialas <victoria.bialas@docker.com>
This commit is contained in:
Victoria Bialas 2017-10-09 11:01:54 -07:00 committed by GitHub
parent c37f8c3e1a
commit a6df37fc99
3 changed files with 14 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
get-started/part2.md
View File

@ -185,6 +185,8 @@ REPOSITORY TAG IMAGE ID
friendlyhello latest 326387cea398 friendlyhello latest 326387cea398
``` ```
> **Tip**: You can use the commands `docker images` or the newer `docker image ls` list images. They give you the same output.
## Run the app ## Run the app
Run the app, mapping your machine's port 4000 to the container's published port Run the app, mapping your machine's port 4000 to the container's published port
@ -239,10 +241,10 @@ CONTAINER ID IMAGE COMMAND CREATED
You'll see that `CONTAINER ID` matches what's on `http://localhost:4000`. You'll see that `CONTAINER ID` matches what's on `http://localhost:4000`.
Now use `docker stop` to end the process, using the `CONTAINER ID`, like so: Now use `docker container stop` to end the process, using the `CONTAINER ID`, like so:
```shell ```shell
docker stop 1fa4ab2cf395 docker container stop 1fa4ab2cf395
``` ```
## Share your image ## Share your image

6
get-started/part3.md
View File

@ -201,12 +201,18 @@ load-balancing; with each request, one of the 5 replicas is chosen, in a
round-robin fashion, to respond. The container IDs will match your output from round-robin fashion, to respond. The container IDs will match your output from
the previous command (`docker container ls -q`). the previous command (`docker container ls -q`).
(Windows 10 PowerShell should already have `curl` available, but if not you can
grab a Linux terminal emulater like [Git
BASH](https://git-for-windows.github.io/){: target="_blank" class="_"} if you
want to try it out. It isn't critical to the taskflow here.)
>**Note**: At this stage, it may take up to 30 seconds for the containers >**Note**: At this stage, it may take up to 30 seconds for the containers
to respond to HTTP requests. This is not indicative of Docker or to respond to HTTP requests. This is not indicative of Docker or
swarm performance, but rather an unmet Redis dependency that we will swarm performance, but rather an unmet Redis dependency that we will
address later in the tutorial. For now, the visitor counter isn't working address later in the tutorial. For now, the visitor counter isn't working
for the same reason; we haven't yet added a service to persist data. for the same reason; we haven't yet added a service to persist data.
## Scale the app ## Scale the app
You can scale the app by changing the `replicas` value in `docker-compose.yml`, You can scale the app by changing the `replicas` value in `docker-compose.yml`,

6
get-started/part4.md
View File

@ -343,8 +343,8 @@ And that's it, the app is deployed on a swarm cluster!
Now you can use the same [docker commands you used in part Now you can use the same [docker commands you used in part
3](/get-started/part3.md#run-your-new-load-balanced-app). Only this time you'll 3](/get-started/part3.md#run-your-new-load-balanced-app). Only this time you'll
see that the containers have been distributed between both `myvm1` and `myvm2`. see that the services (and associated containers) have been distributed between
both `myvm1` and `myvm2`.
``` ```
$ docker stack ps getstartedlab $ docker stack ps getstartedlab
@ -357,6 +357,8 @@ ghii74p9budx test_web.4 username/repo:tag myvm1 Running
0prmarhavs87 test_web.5 username/repo:tag myvm2 Running 0prmarhavs87 test_web.5 username/repo:tag myvm2 Running
``` ```
You can also run `docker container ls` to view container IDs.
> Connecting to VMs with `docker-machine env` and `docker-machine ssh` > Connecting to VMs with `docker-machine env` and `docker-machine ssh`
> >
> * To set your shell to talk to a different machine like `myvm2`, simply re-run > * To set your shell to talk to a different machine like `myvm2`, simply re-run