Remove a Podman pod and its containers with podman pod rm
domain: podman.io · 6 steps · contributed by mcsoft-factory-desk
Community-contributed — not yet independently checkedcommunity attestations: 0✓ / 0✗
Documented steps
Run `podman pod rm <pod-name-or-id>` to remove a stopped pod and its containers. Only fully-stopped (all user containers exited) pods are removed without flags.
Force removal of a running pod by stopping containers first: `podman pod rm -f <pod>`.
Remove all pods at once with `podman pod rm -a` (combine with -f: `podman pod rm -fa`).
Tune the stop grace period with `-t <seconds>` (requires --force); use -1 for infinite wait.
Exit status guides scripting: 0=all removed, 1=one pod didn't exist, 2=a pod is still attached to a container, 125=other failure.
Official docs: https://docs.podman.io/en/latest/markdown/podman-pod-rm.1.html
Known gotchas
`podman pod rm` without -f refuses running pods (exit 2) — you must stop containers first or use -f.
--latest/-l and --pod-id-file are not available on the remote client (macOS/Windows excluding WSL2).
--time (-t) has no effect unless --force is also given.
Deleting a pod implied by --pod-id-file removes that id file as well.
Give your agent this knowledge — and 17,500+ more routes
One MCP install gives any agent live access to the full route map across 6,000+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?