.nh
.TH podman-kill 1
.SH NAME
.PP
podman-kill - Kill the main process in one or more containers

.SH SYNOPSIS
.PP
\fBpodman kill\fP [\fIoptions\fP] [\fIcontainer\fP ...]

.PP
\fBpodman container kill\fP [\fIoptions\fP] [\fIcontainer\fP ...]

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

.SH OPTIONS
.SS \fB--all\fP, \fB-a\fP
.PP
Signal all running and paused containers.

.SS \fB--cidfile\fP=\fIfile\fP
.PP
Read container ID from the specified \fIfile\fP and kill the container.
Can be specified multiple times.

.SS \fB--latest\fP, \fB-l\fP
.PP
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. (This option is not available with the remote Podman client, including Mac and Windows (excluding WSL2) machines)

.SS \fB--signal\fP, \fB-s\fP=\fBsignal\fP
.PP
Signal to send to the container. For more information on Linux signals, refer to \fIsignal(7)\fP\&.
The default is \fBSIGKILL\fP\&.

.SH EXAMPLE
.PP
Kill container with a given name

.PP
.RS

.nf
podman kill mywebserver

.fi
.RE

.PP
Kill container with a given ID

.PP
.RS

.nf
podman kill 860a4b23

.fi
.RE

.PP
Terminate container by sending \fB\fCTERM\fR signal

.PP
.RS

.nf
podman kill --signal TERM 860a4b23

.fi
.RE

.PP
Kill the latest container created by Podman

.PP
.RS

.nf
podman kill --latest

.fi
.RE

.PP
Terminate all containers by sending \fB\fCKILL\fR signal

.PP
.RS

.nf
podman kill --signal KILL -a

.fi
.RE

.PP
Kill container using ID specified in a given files

.PP
.RS

.nf
podman kill --cidfile /home/user/cidfile-1
podman kill --cidfile /home/user/cidfile-1 --cidfile ./cidfile-2

.fi
.RE

.SH SEE ALSO
.PP
\fBpodman(1)\fP, \fBpodman-stop(1)\fP

.SH HISTORY
.PP
September 2017, Originally compiled by Brent Baude bbaude@redhat.com
\[la]mailto:bbaude@redhat.com\[ra]