- bullseye 3.0.1+dfsg1-3+deb11u1
- testing 4.3.1+ds1-6
- unstable 4.3.1+ds1-6+b2
- experimental 4.4.0+ds1-1
podman-stop - Stop one or more running containers
podman stop [options] container ...
podman container stop [options] container ...
Stops one or more containers. You may use container IDs or names as input. The --time switch allows you to specify the number of seconds to wait before forcibly stopping the container after the stop command is issued to the container. The default is 10 seconds. By default, containers are stopped with SIGTERM and then SIGKILL after the timeout. The SIGTERM default can be overridden by the image used to create the container and also via command line when creating the container.
Stop all running containers. This does not include paused containers.
Read container ID from the specified file and remove the container. Can be specified multiple times.
Ignore errors when specified containers are not in the container store. A user might have decided to manually remove a container which would lead to a failure during the ExecStop directive of a systemd service referencing that container.
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.
The latest option is not supported on the remote client.
Time to wait before forcibly stopping the container
$ podman stop mywebserver
$ podman stop 860a4b235279
$ podman stop mywebserver 860a4b235279
$ podman stop --cidfile /home/user/cidfile-1
$ podman stop --cidfile /home/user/cidfile-1 --cidfile ./cidfile-2
$ podman stop --time 2 860a4b235279
$ podman stop -a
$ podman stop --latest
September 2018, Originally compiled by Brent Baude firstname.lastname@example.org ⟨mailto:email@example.com⟩