--all, -a¶

Remove all containers. Can be used in conjunction with -f as well.

--cidfile=file¶

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

--depend¶

Remove selected container and recursively remove all containers that depend on it.

--filter=filter¶

Filter what containers remove. Multiple filters can be given with multiple uses of the --filter flag. Filters with the same key work inclusive with the only exception being label which is exclusive. Filters with different keys always work exclusive.

Valid filters are listed below:

--force, -f¶

Force the removal of running and paused containers. Forcing a container removal also removes containers from container storage even if the container is not known to podman. Containers could have been created by a different container engine. In addition, forcing can be used to remove unusable containers, e.g. containers whose OCI runtime has become unavailable.

--ignore, -i¶

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.

--latest, -l¶

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)

--time, -t=seconds¶

Seconds to wait before forcibly stopping the container.

The --force option must be specified to use the --time option.

--volumes, -v¶

Remove anonymous volumes associated with the container. This does not include named volumes created with podman volume create, or the --volume option of podman run and podman create.