.nh
.TH podman\-pod\-kill(1)
.SH NAME
.PP
podman\-pod\-kill \- Kill the main process of each container in one or more pods

.SH SYNOPSIS
.PP
\fBpodman pod kill\fP [\fIoptions\fP] \fIpod\fP ...

.SH DESCRIPTION
.PP
The main process of each container inside the pods specified will be sent SIGKILL, or any signal specified with option \-\-signal.

.SH OPTIONS
.SS \fB\-\-all\fP, \fB\-a\fP
.PP
Sends signal to all containers associated with a pod.

.SS \fB\-\-latest\fP, \fB\-l\fP
.PP
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.

.PP
The latest option is not supported on the remote client.

.SS \fB\-\-signal\fP, \fB\-s\fP
.PP
Signal to send to the containers in the pod. For more information on Linux signals, refer to \fIman signal(7)\fP\&.

.SH EXAMPLE
.PP
podman pod kill mywebserver

.PP
podman pod kill 860a4b23

.PP
podman pod kill \-\-signal TERM 860a4b23

.PP
podman pod kill \-\-latest

.PP
podman pod kill \-\-all

.SH SEE ALSO
.PP
podman\-pod(1), podman\-pod\-stop(1)

.SH HISTORY
.PP
July 2018, Originally compiled by Peter Hunt pehunt@redhat.com
\[la]mailto:pehunt@redhat.com\[ra]