podman-kill - Man Page

Kill the main process in one or more containers

Synopsis

podman kill [options] [container ...]

podman container kill [options] [container ...]

Description

The main process inside each container specified is sent SIGKILL or any signal specified with the --signal option.

Options

--all, -a

Signal all running and paused containers.

--cidfile=file

Read container ID from the specified file and kill the container. Can be specified multiple times.

--latest, -l

Instead of providing the container name or ID, use the last created container. Note: the last started container can be from other users of Podman on the host machine. (This option is not available with the remote Podman client, including Mac and Windows (excluding WSL2) machines)

--signal, -s=signal

Signal to send to the container. For more information on Linux signals, refer to signal(7). The default is SIGKILL.

Example

Kill container with a given name:

podman kill mywebserver

Kill container with a given ID:

podman kill 860a4b23

Terminate container by sending TERM signal:

podman kill --signal TERM 860a4b23

Kill the latest container. (This option is not available with the remote Podman client, including Mac and Windows (excluding WSL2) machines):

podman kill --latest

Terminate all containers by sending KILL signal:

podman kill --signal KILL -a

Kill containers using ID specified in a given files:

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

See Also

podman(1), podman-stop(1)

History

September 2017, Originally compiled by Brent Baude bbaude@redhat.com ⟨mailto:bbaude@redhat.com⟩

Referenced By

podman(1), podman-container(1), podman-create(1), podman-remote(1), podman-run(1).

The man pages docker-container-kill(1), docker-kill(1) and podman-container-kill(1) are aliases of podman-kill(1).