mirror of
https://github.com/containers/podman.git
synced 2025-06-08 00:00:51 +08:00
bc48211924
Escape the two dashes, otherwise they are combined into one long dash. I tested that this change is safe and still renders correctly on github and with the man pages. This commit also contains a small change to make it build locally. Assuming you have the dependencies installed you can do: ``` cd docs make html ``` Preview the html files in docs/build/html with `python -m http.server 8000 --directory build/html`. Fixes containers/podman.io#373 Signed-off-by: Paul Holzinger <paul.holzinger@web.de>
44 lines
1.1 KiB
Markdown
44 lines
1.1 KiB
Markdown
% podman-pod-kill(1)
|
|
|
|
## NAME
|
|
podman\-pod\-kill - Kill the main process of each container in one or more pods
|
|
|
|
## SYNOPSIS
|
|
**podman pod kill** [*options*] *pod* ...
|
|
|
|
## DESCRIPTION
|
|
The main process of each container inside the pods specified will be sent SIGKILL, or any signal specified with option --signal.
|
|
|
|
## OPTIONS
|
|
#### **\-\-all**, **-a**
|
|
|
|
Sends signal to all containers associated with a pod.
|
|
|
|
#### **\-\-latest**, **-l**
|
|
|
|
Instead of providing the pod name or ID, use the last created pod. If you use methods other than Podman
|
|
to run pods such as CRI-O, the last started pod could be from either of those methods. (This option is not available with the remote Podman client)
|
|
|
|
#### **\-\-signal**, **-s**
|
|
|
|
Signal to send to the containers in the pod. For more information on Linux signals, refer to *man signal(7)*.
|
|
|
|
|
|
## EXAMPLE
|
|
|
|
podman pod kill mywebserver
|
|
|
|
podman pod kill 860a4b23
|
|
|
|
podman pod kill --signal TERM 860a4b23
|
|
|
|
podman pod kill --latest
|
|
|
|
podman pod kill --all
|
|
|
|
## SEE ALSO
|
|
podman-pod(1), podman-pod-stop(1)
|
|
|
|
## HISTORY
|
|
July 2018, Originally compiled by Peter Hunt <pehunt@redhat.com>
|