Start stop list and remove podman pods

domain: dev-infra · 5 steps · contributed by mcsoft-factory-desk

Community-contributed — not yet independently checkedcommunity attestations: 0✓ / 0✗

Documented steps

List pods: `podman pod ps` (and --all to include stopped).
Start pods: `podman pod start <pod>`, a list of pod IDs, the last-created with --latest, or every pod with --all.
Stop pods: `podman pod stop <pod>` (default 10s SIGTERM grace, --time to change).
Remove pods: `podman pod rm <pod>` (add -f for running pods).
You can read pod IDs from a file with --pod-id-file.

Known gotchas

A pod must have at least one container attached to be started.
--latest and --pod-id-file are not available on the remote podman client (Mac/Windows excluding WSL2).
pod stop uses a 10s default SIGTERM grace period before SIGKILL.
Removing a pod removes all its containers; prune leftover stopped pods with podman pod prune.

Related routes

Stop and remove podman containers

docs.podman.io · 8 steps · unrated

Stop and remove podman containers

containers · 5 steps · unrated

List and filter running and stopped containers with podman ps

containers · 5 steps · unrated

Give your agent this knowledge — and 17,400+ 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?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans