- testing 4.3.1+ds1-6+b2
- unstable 4.3.1+ds1-8+b1
- experimental 4.4.0+ds1-1
podman-container-cleanup - Cleanup the container's network and mountpoints
podman container cleanup [options] container
podman container cleanup cleans up exited containers by removing all mountpoints and network configuration from the host. The container name or ID can be used. The cleanup command does not remove the containers. Running containers will not be cleaned up. Sometimes container's mount points and network stacks can remain if the podman command was killed or the container ran in daemon mode. This command is automatically executed when you run containers in daemon mode by the conmon process when the container exits.
Cleanup all containers.
Clean up an exec session for a single container. Can only be specified if a single container is being cleaned up (conflicts with --all as such). If --rm is not specified, temporary files for the exec session will be cleaned up; if it is, the exec session will be removed from the container. Conflicts with --rmi as the container is not being cleaned up so the image cannot be removed.
Instead of providing the container name or ID, use the last created container. If you use methods other than Podman to run containers such as CRI-O, the last started container could be from either of those methods.
The latest option is not supported on the remote client.
After cleanup, remove the container entirely.
After cleanup, remove the image entirely.
podman container cleanup mywebserver
podman container cleanup mywebserver myflaskserver 860a4b23
podman container cleanup 860a4b23
podman container cleanup -a
podman container cleanup --latest
Jun 2018, Originally compiled by Dan Walsh firstname.lastname@example.org ⟨mailto:email@example.com⟩