podman-pod-rm(1)

💖 podman-pod-rm(1) — General Commands Manual 💖

okay bestie, this is the podman-pod-rm page from the General Commands Manual and it's literally about yeeting pods into the void 🫶

---

✨ NAME ✨

podman-pod-rm — remove one or more stopped pods and containers. that's it. that's the whole job. bye bye pod 👋

---

✨ SYNOPSIS ✨

podman pod rm [options] pod

---

🌸 DESCRIPTION 🌸

so here's the tea: podman pod rm removes one or more stopped pods and their containers off your host. you can point at the pod by name or by ID, whichever one you've got handy, no judgement 💅

and if you pass the -f option? it stops all the containers first and then removes them before it removes the pod. main character energy, honestly.

also: if every container that a user added is sitting in an exited state, the pod gets removed. that's the vibe check, and it passed ✨

---

👑 OPTIONS 👑

• --all, -a — remove all the pods. and yes, you can absolutely run this alongside -f too, they're besties 🫶
• --force, -f — stop the running containers, delete all the stopped containers, and then remove the pod. no survivors, periodt 💀
• --ignore, -i — ignore errors when the pods you named aren't in the container store. like, real scenario: a user might've decided to manually remove a pod, which then makes things blow up during the ExecStop directive of a systemd service that references that pod. so this option is the "it's fine, we move" button 🙈
• --latest, -l — instead of typing a pod name or ID, just use the last created pod. iconic, lazy, we love her.

heads up: the last started pod can be from other users of Podman on the same host machine. also this option is not available with the remote Podman client, including Mac and Windows machines (WSL2 excluded) 😭

• --pod-id-file=file — read the pod ID out of the specified file and rm that pod. you can specify this multiple times, go off 🎀

if specified, the pod-id-file is removed along with the pod. so the file leaves with the pod, ride or die 🌈

• --time, -t=seconds — how many seconds to wait before forcibly stopping the running containers inside the pod. use -1 for an infinite wait ⏳

the --force option must be specified in order to use the --time option. non-negotiable, that's the rule 🔥

---

🌟 EXAMPLE 🌟

remove a pod with a given name:

podman pod rm mywebserverpod

remove multiple pods with given names and/or IDs:

podman pod rm mywebserverpod myflaskserverpod 860a4b23

forcefully remove a pod with a given ID:

podman pod rm -f 860a4b23

forcefully remove all pods:

podman pod rm -f -a
podman pod rm -fa

remove a pod using the ID specified in a given file:

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

---

⭐ Exit Status ⭐

• 0 — all specified pods removed ✨ slay
• 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 💀

---

🦋 SEE ALSO 🦋

podman(1), podman-pod(1)

---

🎀 HISTORY 🎀

July 2018, originally compiled by Peter Hunt pehunt@redhat.com ⟨mailto:pehunt@redhat.com⟩ — shoutout to the og 💜

---

and that's the whole page bestie, you ate 🍓 this was podman-pod-rm(1) from the General Commands Manual, July 2018 edition, mwah 😭💖