podman-container-cleanup - Online Linux Manual PageSection : 1
NAMEpodman-container-cleanup - Clean up the container's network and mountpoints
SYNOPSISpodman container cleanup [options] container [container ...]
DESCRIPTIONpodman 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 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 containers are run in daemon mode by the conmon process when the container exits.
OPTIONS
--all, -aClean up all containers.
The default is false.
IMPORTANT: This OPTION does not need a container name or ID as input argument.
--exec=sessionClean 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.
*IMPORTANT: Conflicts with --rmi as the container is not being cleaned up so the image cannot be removed.*
--latest, -lInstead of providing the container ID or name, use the last created container. If other methods than Podman are used to run containers such as CRI-O, the last started container could be from either of those methods.
The default is false.
IMPORTANT: This OPTION is not available with the remote Podman client, including Mac and Windows (excluding WSL2) machines. This OPTION does not need a container name or ID as input argument.
--rmAfter cleanup, remove the container entirely.
The default is false.
--rmiAfter cleanup, remove the image entirely.
The default is false.
EXAMPLESClean up the container "mywebserver". $ podman container cleanup mywebserver
Clean up the containers with the names "mywebserver", "myflaskserver", "860a4b23". $ podman container cleanup mywebserver myflaskserver 860a4b23
SEE ALSOpodman(1), podman-container(1), conmon(8)
HISTORYJun 2018, Originally compiled by Dan Walsh dwalsh@redhat.com ⟨mailto:dwalsh@redhat.com⟩ 0
Johanes Gumabo
Data Size : 12,104 byte
man-podman-container-cleanup.1Build : 2024-12-05, 20:55 :
Visitor Screen : x
Visitor Counter ( page / site ) : 3 / 182,077
Visitor ID : :
Visitor IP : 3.141.192.174 :
Visitor Provider : AMAZON-02 :
Provider Position ( lat x lon ) : 39.962500 x -83.006100 : x
Provider Accuracy Radius ( km ) : 1000 :
Provider City : Columbus :
Provider Province : Ohio , : ,
Provider Country : United States :
Provider Continent : North America :
Visitor Recorder : Version :
Visitor Recorder : Library :
Online Linux Manual Page : Version : Online Linux Manual Page - Fedora.40 - march=x86-64 - mtune=generic - 24.12.05
Online Linux Manual Page : Library : lib_c - 24.10.03 - march=x86-64 - mtune=generic - Fedora.40
Online Linux Manual Page : Library : lib_m - 24.10.03 - march=x86-64 - mtune=generic - Fedora.40
Data Base : Version : Online Linux Manual Page Database - 24.04.13 - march=x86-64 - mtune=generic - fedora-38
Data Base : Library : lib_c - 23.02.07 - march=x86-64 - mtune=generic - fedora.36
Very long time ago, I have the best tutor, Wenzel Svojanovsky . If someone knows the email address of Wenzel Svojanovsky , please send an email to johanes_gumabo@yahoo.co.id .
If error, please print screen and send to johanes_gumabo@yahoo.co.id
Under development. Support me via PayPal.