mirror of
https://github.com/containers/podman.git
synced 2025-05-25 19:16:59 +08:00
7b08aa78e4
It is desirable to have a shortcut for the most recently created container. We can now use "**latest" to represent the most recent container instead of its container ID or name. For example: Signed-off-by: baude <bbaude@redhat.com> Closes: #179 Approved by: baude
39 lines
978 B
Markdown
39 lines
978 B
Markdown
% podman(1) podman-kill- Kill one or more containers with a signal
|
|
% Brent Baude
|
|
# podman-kill"1" "September 2017" "podman"
|
|
|
|
## 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
|
|
**--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.
|
|
|
|
**--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
|
|
|
|
## SEE ALSO
|
|
podman(1), podman-stop(1)
|
|
|
|
## HISTORY
|
|
September 2017, Originally compiled by Brent Baude <bbaude@redhat.com>
|