q3k
/
docker-cli-openbsd
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Set exit code of old running container as 137 

Signed-off-by: Chun Chen <chenchun.feed@gmail.com>
master
Chun Chen 2015-06-12 16:20:23 +08:00 committed by Tibor Vass
parent 2e3dc04935
commit 686e6d31e7
1 changed files with 15 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
docs/reference/commandline/cli.md
View File

@ -1845,6 +1845,21 @@ The currently supported filters are:
This shows all the containers that have exited with status of '0'
##### Killed containers
You can use a filter to locate containers that exited with status of `137` meaning a `SIGKILL(9)` killed them.
$ 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 a result in `137` status:
* the `init` process of the container is killed manually
* `docker kill` kills the container
* Docker daemon restarts which kills all old running containers
## pull
Usage: docker pull [OPTIONS] NAME[:TAG] | [REGISTRY_HOST[:REGISTRY_PORT]/]NAME[:TAG]