Provided by: podman_3.4.4+ds1-1ubuntu1_amd64 bug


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


       podman pod rm [options] pod


       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. If all containers added by the user are in an exited state, the
       pod will be removed.


   --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. (This option is  not
       available with the remote Podman client)

   --force, -f
       Stop running containers and delete all stopped containers before removal of pod.

       Read pod ID from the specified file and remove the pod.  Can be specified multiple times.


       podman pod rm mywebserverpod

       podman pod rm mywebserverpod myflaskserverpod 860a4b23

       podman pod rm -f 860a4b23

       podman pod rm -f -a

       podman pod rm -fa

       podman pod rm --pod-id-file /path/to/id/file

Exit Status

       0   All specified pods removed

       1   One of the specified pods did not exist, and no other failures

       2   One of the specified pods is attached to a container

       125 The command fails for any other reason




       July 2018, Originally compiled by Peter Hunt pehunt@redhat.commailto:pehunt@redhat.compodman-pod-rm(1)()