Files
podman/docs/source/markdown/podman-pod-rm.1.md
Qi Wang d9400cced2 Remove containers when pruning a stopped pod.
This path allows pod prune & pod rm to remove stopped containers in the pod before deleting the pod.
PrunePods and RemovePod should be able to remove containers without force removal of stopped pods.

Signed-off-by: Qi Wang <qiwan@redhat.com>
2019-11-26 13:19:31 -05:00

1.2 KiB

% podman-pod-rm(1)

NAME

podman-pod-rm - Remove one or more stopped pods and containers

SYNOPSIS

podman pod rm [options] pod

DESCRIPTION

podman pod rm will remove one or more stopped pods and their containers from the host. The pod name or ID can be used. The -f option stops all containers and then removes them before removing the pod.

OPTIONS

--all, -a

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

--ignore, -i

Ignore errors when specified pods are not in the container store. A user might have decided to manually remove a pod which would lead to a failure during the ExecStop directive of a systemd service referencing that pod.

--latest, -l

Instead of providing the pod name or ID, remove the last created pod.

The latest option is not supported on the remote client.

--force, -f

Stop running containers and delete all stopped containers before removal of pod.

EXAMPLE

podman pod rm mywebserverpod

podman pod rm mywebserverpod myflaskserverpod 860a4b23

podman pod rm -f 860a4b23

podman pod rm -f -a

podman pod rm -fa

SEE ALSO

podman-pod(1)

HISTORY

July 2018, Originally compiled by Peter Hunt pehunt@redhat.com