mirror of
https://github.com/containers/podman
synced 2024-10-21 09:45:32 +00:00
0b34b4a59c
podman system prune would leave pods be, and not prune them if they were stopped. Fix this by adding a `podman pod prune` command that prunes stopped pods similarly to containers. Signed-off-by: Peter Hunt <pehunt@redhat.com>
38 lines
1.1 KiB
Markdown
38 lines
1.1 KiB
Markdown
% podman-system-prune(1) podman
|
|
|
|
## NAME
|
|
podman\-system\-prune - Remove all unused container, image and volume data
|
|
|
|
## SYNOPSIS
|
|
**podman system prune**
|
|
[**-all**|**--a**]
|
|
[**-force**|**--f**]
|
|
[**-help**|**--h**]
|
|
[**-volumes**|**--v**]
|
|
|
|
## DESCRIPTION
|
|
**podman system prune** removes all unused containers (both dangling and unreferenced), pods and optionally, volumes from local storage.
|
|
|
|
With the `all` option, you can delete all unused images. Unused images are dangling images as well as any image that does not have any containers based on it.
|
|
|
|
By default, volumes are not removed to prevent important data from being deleted if there is currently no container using the volume. Use the --volumes flag when running the command to prune volumes as well.
|
|
|
|
## OPTIONS
|
|
**--all, -a**
|
|
|
|
Remove all unused images not just dangling ones.
|
|
|
|
**--force, -f**
|
|
|
|
Do not prompt for confirmation
|
|
|
|
**--volumes**
|
|
|
|
Prune volumes not used by at least one container
|
|
|
|
## SEE ALSO
|
|
podman(1), podman-image-prune(1), podman-container-prune(1), podman-pod-prune(1), podman-volume-prune(1)
|
|
|
|
# HISTORY
|
|
February 2019, Originally compiled by Dan Walsh (dwalsh at redhat dot com)
|