Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Added a command for getting the service #8189

Merged
merged 4 commits into from Feb 14, 2019
Merged

Added a command for getting the service #8189

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
76a43be
Added a command for getting the service
chilupa Feb 8, 2019
7ee7214
Incorporate suggested content addition
bermudezmt Feb 14, 2019
ee821c5
Final cleanup
bermudezmt Feb 14, 2019
1e096d0
Update part3.md
Feb 14, 2019
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
26 changes: 24 additions & 2 deletions get-started/part3.md
View file
Open in desktop
Expand Up @@ -143,18 +143,28 @@ 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
replicas, image name, and exposed ports.

Alternatively, you can run `docker stack services`, followed by the name of
your stack. The following example command lets you view all services associated with the
`getstartedlab` stack:

```bash
docker stack services getstartedlab
ID NAME MODE REPLICAS IMAGE PORTS
bqpve1djnk0x getstartedlab_web replicated 5/5 username/repo:tag *:4000->80/tcp
```

A single container running in a service is called a **task**. Tasks are given unique
IDs that numerically increment, up to the number of `replicas` you defined in
`docker-compose.yml`. List the tasks for your service:

```shell
```bash
docker service ps getstartedlab_web
```

Tasks also show up if you just list all the containers on your system, though that
is not filtered by service:

```shell
```bash
docker container ls -q
```

Expand All @@ -168,6 +178,18 @@ 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
the previous command (`docker container ls -q`).

To view all tasks of a stack, you can run `docker stack ps` followed by your app name, as shown in the following example:

```bash
docker stack ps getstartedlab
ID NAME IMAGE NODE DESIRED STATE CURRENT STATE ERROR PORTS
uwiaw67sc0eh getstartedlab_web.1 username/repo:tag docker-desktop Running Running 9 minutes ago
sk50xbhmcae7 getstartedlab_web.2 username/repo:tag docker-desktop Running Running 9 minutes ago
c4uuw5i6h02j getstartedlab_web.3 username/repo:tag docker-desktop Running Running 9 minutes ago
0dyb70ixu25s getstartedlab_web.4 username/repo:tag docker-desktop Running Running 9 minutes ago
aocrb88ap8b0 getstartedlab_web.5 username/repo:tag docker-desktop Running Running 9 minutes ago
```

> Running Windows 10?
>
> Windows 10 PowerShell should already have `curl` available, but if not you can
Expand Down