Skip to content

Commit

Permalink
Restore missing ps example for killed containers
Browse files Browse the repository at this point in the history
This example was added in b0b2f97,
but got lost during splitting up the cli.md docs into separate files;
561bfb2

This restores the missing example.

Signed-off-by: Sebastiaan van Stijn <[email protected]>
(cherry picked from commit 8d5818a)
Signed-off-by: Sebastiaan van Stijn <[email protected]>
  • Loading branch information
thaJeztah committed Aug 17, 2016
1 parent e24421a commit 2875711
Showing 1 changed file with 17 additions and 0 deletions.
17 changes: 17 additions & 0 deletions docs/reference/commandline/ps.md
Original file line number Diff line number Diff line change
Expand Up @@ -138,6 +138,23 @@ ea09c3c82f6e registry:latest /srv/run.sh 2 weeks ago
48ee228c9464 fedora:20 bash 2 weeks ago Exited (0) 2 weeks ago tender_torvalds
```

#### Killed containers

You can use a filter to locate containers that exited with status of `137`
meaning a `SIGKILL(9)` killed them.

```bash
$ docker ps -a --filter 'exited=137'
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
b3e1c0ed5bfe ubuntu:latest "sleep 1000" 12 seconds ago Exited (137) 5 seconds ago grave_kowalevski
a2eb5558d669 redis:latest "/entrypoint.sh redi 2 hours ago Exited (137) 2 hours ago sharp_lalande
Any of these events result in a `137` status:
* the `init` process of the container is killed manually
* `docker kill` kills the container
* Docker daemon restarts which kills all running containers
#### Status
The `status` filter matches containers by status. You can filter using
Expand Down

0 comments on commit 2875711

Please sign in to comment.