Files
podman/docs/source/markdown/podman-volume-rm.1.md
Daniel J Walsh 22474095ab Fix handling of remove of bogus volumes, networks and Pods
In podman containers rm and podman images rm, the commands
exit with error code 1 if the object does not exists.

This PR implements similar functionality to volumes, networks, and Pods.

Similarly if volumes or Networks are in use by other containers, and return
exit code 2.

Signed-off-by: Daniel J Walsh <dwalsh@redhat.com>
2020-09-29 15:52:43 -04:00

56 lines
1.2 KiB
Markdown

% podman-volume-rm(1)
## NAME
podman\-volume\-rm - Remove one or more volumes
## SYNOPSIS
**podman volume rm** [*options*] *volume* [...]
## DESCRIPTION
Removes one or more volumes. Only volumes that are not being used will be removed.
If a volume is being used by a container, an error will be returned unless the **--force**
flag is being used. To remove all volumes, use the **--all** flag.
Volumes can be removed individually by providing their full name or a unique partial name.
## OPTIONS
**-a**, **--all**
Remove all volumes.
**-f**, **--force**
Remove a volume by force.
If it is being used by containers, the containers will be removed first.
**--help**
Print usage statement
## EXAMPLES
```
$ podman volume rm myvol1 myvol2
$ podman volume rm --all
$ podman volume rm --force myvol
```
## Exit Status
**0** All specified volumes removed
**1** One of the specified volumes did not exist, and no other failures
**2** One of the specified volumes is being used by a container
**125** The command fails for any other reason
## SEE ALSO
podman-volume(1)
## HISTORY
November 2018, Originally compiled by Urvashi Mohnani <umohnani@redhat.com>