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

Final cleanup

This commit is contained in:
Maria Bermudez 2019-02-13 18:10:50 -08:00 committed by GitHub
parent 7ee7214028
commit ee821c590f
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
get-started/part3.md
View File

@ -132,13 +132,7 @@ docker stack deploy -c docker-compose.yml getstartedlab
Our single service stack is running 5 container instances of our deployed image Our single service stack is running 5 container instances of our deployed image
on one host. Let's investigate. on one host. Let's investigate.
To get the services for a service stack, get the service ID for the one service in our application: Get the service ID for the one service in our application:
```shell
docker stack services getstartedlab
```
If you are using **Kubernetes**, get the service ID for the one service in our application:
```shell ```shell
docker service ls docker service ls
@ -149,7 +143,7 @@ named it the same as shown in this example, the name is
`getstartedlab_web`. The service ID is listed as well, along with the number of `getstartedlab_web`. The service ID is listed as well, along with the number of
replicas, image name, and exposed ports. replicas, image name, and exposed ports.
You can also run `docker stack services`, followed by the name of Alternatively, you can run `docker stack services`, followed by the name of
your stack. The following example command lets you view all the services associated with the your stack. The following example command lets you view all the services associated with the
`getstartedlab` stack: `getstartedlab` stack:
@ -184,7 +178,7 @@ load-balancing; with each request, one of the 5 tasks is chosen, in a
round-robin fashion, to respond. The container IDs match your output from round-robin fashion, to respond. The container IDs match your output from
the previous command (`docker container ls -q`). the previous command (`docker container ls -q`).
Additionally, you can run `docker stack ps` to view all tasks of a stack. To view all tasks of a stack, you can run `docker stack ps` followed by your app name:
```bash ```bash
docker stack ps getstartedlab docker stack ps getstartedlab