podman-rm - Online Linux Manual PageSection : 1
NAMEpodman-rm - Remove one or more containers
SYNOPSISpodman rm [options] container podman container rm [options] container
DESCRIPTIONpodman rm will remove one or more containers from the host. The container name or ID can be used. This does not remove images. Running or unusable containers will not be removed without the -f option.
OPTIONS
--all, -aRemove all containers. Can be used in conjunction with -f as well.
--cidfile=fileRead container ID from the specified file and rm the container. Can be specified multiple times.
--dependRemove selected container and recursively remove all containers that depend on it.
--filter=filterFilter what containers remove. Multiple filters can be given with multiple uses of the --filter flag. Filters with the same key work inclusive with the only exception being label which is exclusive. Filters with different keys always work exclusive. Valid filters are listed below: FilterDescription id [ID] Container's ID (accepts regex) name [Name] Container's name (accepts regex) label [Key] or [Key=Value] Label assigned to a container exited[Int] Container's exit code status [Status] Container's status: 'created', 'exited', 'paused', 'running', 'unknown' ancestor [ImageName] Image or descendant used to create container before [ID] or [Name] Containers created before this container since [ID] or [Name] Containers created since this container volume [VolumeName] or [MountpointDestination] Volume mounted in container health[Status] healthy or unhealthy pod [Pod] name or full or partial ID of pod network [Network] name or full ID of network
--force, -fForce the removal of running and paused containers. Forcing a container removal also removes containers from container storage even if the container is not known to podman. Containers could have been created by a different container engine. In addition, forcing can be used to remove unusable containers, e.g. containers whose OCI runtime has become unavailable.
--ignore, -iIgnore errors when specified containers are not in the container store. A user might have decided to manually remove a container which would lead to a failure during the ExecStop directive of a systemd service referencing that container. Further ignore when the specified --cidfile does not exist as it may have already been removed along with the container.
--latest, -lInstead of providing the container name or ID, use the last created container. Note: the last started container could be from other users of Podman on the host machine. (This option is not available with the remote Podman client, including Mac and Windows (excluding WSL2) machines)
--time, -t=secondsSeconds to wait before forcibly stopping the container. The --force option must be specified to use the --time option.
--volumes, -vRemove anonymous volumes associated with the container. This does not include named volumes created with podman volume create, or the --volume option of podman run and podman create.
EXAMPLERemove container with a given name $ podman rm mywebserver
Remove container with a given name and all of the containers that depend on it $ podman rm --depend mywebserver
Remove multiple containers with given names or IDs $ podman rm mywebserver myflaskserver 860a4b23
Remove multiple containers with IDs read from files $ podman rm --cidfile ./cidfile-1 --cidfile /home/user/cidfile-2
Forcibly remove container with a given ID $ podman rm -f 860a4b23
Remove all containers regardless of the run state $ podman rm -f -a
Forcibly remove the last created container $ podman rm -f --latest
Exit Status0 All specified containers removed 1 One of the specified containers did not exist, and no other failures 2 One of the specified containers is paused or running 125 The command fails for any other reason
SEE ALSOpodman(1), crio(8)
HISTORYAugust 2017, Originally compiled by Ryan Cole rycole@redhat.com ⟨mailto:rycole@redhat.com⟩ 0
Johanes Gumabo
Data Size : 23,513 byte
man-podman-container-rm.1Build : 2024-12-05, 20:55 :
Visitor Screen : x
Visitor Counter ( page / site ) : 3 / 182,005
Visitor ID : :
Visitor IP : 18.226.187.224 :
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.