Add --all flag to podman kill

Signed-off-by: Daniel J Walsh <dwalsh@redhat.com>
This commit is contained in:
Daniel J Walsh
2018-09-29 17:27:58 +02:00
parent 1859e35c76
commit 249a51a2fc
4 changed files with 59 additions and 25 deletions

View File

@ -10,6 +10,10 @@ podman\-kill - Kills one or more containers with a signal
The main process inside each container specified will be sent SIGKILL, or any signal specified with option --signal.
## OPTIONS
**--all, -a**
Signal all running containers. This does not include paused containers.
**--latest, -l**
Instead of providing the container name or ID, use the last created container. If you use methods other than Podman
@ -30,6 +34,8 @@ podman kill --signal TERM 860a4b23
podman kill --latest
podman kill --signal KILL -a
## SEE ALSO
podman(1), podman-stop(1)

View File

@ -15,10 +15,6 @@ container and also via command line when creating the container.
## OPTIONS
**--timeout, --time, t**
Timeout to wait before forcibly stopping the container
**--all, -a**
Stop all running containers. This does not include paused containers.
@ -28,6 +24,10 @@ Stop all running containers. This does not include paused containers.
Instead of providing the container name or ID, use the last created container. If you use methods other than Podman
to run containers such as CRI-O, the last started container could be from either of those methods.
**--timeout, --time, t**
Timeout to wait before forcibly stopping the container
## EXAMPLE
podman stop mywebserver