mirror of
https://github.com/containers/podman.git
synced 2025-09-14 20:13:22 +08:00
f2462ca59e
man-pages(7) has [1]: > For commands, this shows the syntax of the command and its arguments > (including options); boldface is used for as-is text and italics are > used to indicate replaceable arguments. Brackets ([]) surround > optional arguments, vertical bars (|) separate choices, and ellipses > (...) can be repeated. I've adjusted our SYNOPSIS entries to match that formatting, and generally tried to make them more consistent with the precedent set by the man-pages project. Outside of the SYNOPSIS entry, I prefer using backticks for literals, although in some places I've left the ** bolding to keep things visually similar to a nearby SYNOPSIS entry. [1]: http://man7.org/linux/man-pages/man7/man-pages.7.html Signed-off-by: W. Trevor King <wking@tremily.us> Closes: #1027 Approved by: rhatdan
38 lines
876 B
Markdown
38 lines
876 B
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
|
|
**--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>
|