fea78d5530
Currenly if a user specifies the name or ID of an external storage container, we report an error to them. buildah from scratch working-container-2 podman rm working-container-2 Error: no container with name or ID working-container-2 found: no such container Since the user specified the correct name and the container is in storage we force them to specify --storage to remove it. This is a bad experience for the user. This change will just remove the container from storage. If the container is known by libpod, it will remove the container from libpod as well. The podman rm --storage option has been deprecated, and removed from docs. Also cleaned documented options that are not available to podman-remote. Signed-off-by: Daniel J Walsh <dwalsh@redhat.com>
2.7 KiB
% podman-rm(1)
NAME
podman-rm - Remove one or more containers
SYNOPSIS
podman rm [options] container
podman container rm [options] container
DESCRIPTION
podman 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, -a
Remove all containers. Can be used in conjunction with -f as well.
--cidfile
Read container ID from the specified file and remove the container. Can be specified multiple times.
--force, -f
Force 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, -i
Ignore 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.
--latest, -l
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.
--volumes, -v
Remove 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.
EXAMPLE
Remove a container by its name mywebserver
$ podman rm mywebserver
Remove several containers by name and container id.
$ podman rm mywebserver myflaskserver 860a4b23
Remove several containers reading their IDs from files.
$ podman rm --cidfile ./cidfile-1 --cidfile /home/user/cidfile-2
Forcibly remove a container by container ID.
$ podman rm -f 860a4b23
Remove all containers regardless of its run state.
$ podman rm -f -a
Forcibly remove the latest container created.
$ podman rm -f --latest
Exit Status
0 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 ALSO
podman(1), podman-image-rm(1), podman-ps(1), podman-build(1), buildah(1), cri-o(1)
HISTORY
August 2017, Originally compiled by Ryan Cole rycole@redhat.com