46 lines
1.0 KiB
Markdown
46 lines
1.0 KiB
Markdown
% podman-kill(1)
|
|
|
|
## NAME
|
|
podman\-kill - Kills one or more containers with a signal
|
|
|
|
## SYNOPSIS
|
|
**podman kill** [*options*] [*container* ...]
|
|
|
|
## DESCRIPTION
|
|
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
|
|
to run containers such as CRI-O, the last started container could be from either of those methods.
|
|
|
|
The latest option is not supported on the remote client.
|
|
|
|
**--signal, s**
|
|
|
|
Signal to send to the container. For more information on Linux signals, refer to *man signal(7)*.
|
|
|
|
|
|
## EXAMPLE
|
|
|
|
podman kill mywebserver
|
|
|
|
podman kill 860a4b23
|
|
|
|
podman kill --signal TERM 860a4b23
|
|
|
|
podman kill --latest
|
|
|
|
podman kill --signal KILL -a
|
|
|
|
## SEE ALSO
|
|
podman(1), podman-stop(1)
|
|
|
|
## HISTORY
|
|
September 2017, Originally compiled by Brent Baude <bbaude@redhat.com>
|