6c5c34d50d
This fix tries to address the issue in raised #23367 where an out-of-band volume driver deletion leaves some data in docker. This prevent the reuse of deleted volume names (by out-of-band volume driver like flocker). This fix adds a `--force` field in `docker volume rm` to forcefully purge the data of the volume that has already been deleted. Related documentations have been updated. This fix is tested manually with flocker, as is specified in #23367. An integration test has also been added for the scenario described. This fix fixes #23367. Signed-off-by: Yong Tang <yong.tang.github@outlook.com>
36 lines
725 B
Markdown
36 lines
725 B
Markdown
<!--[metadata]>
|
|
+++
|
|
title = "volume rm"
|
|
description = "the volume rm command description and usage"
|
|
keywords = ["volume, rm"]
|
|
[menu.main]
|
|
parent = "smn_cli"
|
|
+++
|
|
<![end-metadata]-->
|
|
|
|
# volume rm
|
|
|
|
```markdown
|
|
Usage: docker volume rm [OPTIONS] VOLUME [VOLUME...]
|
|
|
|
Remove one or more volumes
|
|
|
|
Aliases:
|
|
rm, remove
|
|
|
|
Options:
|
|
-f, --force Force the removal of one or more volumes
|
|
--help Print usage
|
|
```
|
|
|
|
Remove one or more volumes. You cannot remove a volume that is in use by a container.
|
|
|
|
$ docker volume rm hello
|
|
hello
|
|
|
|
## Related information
|
|
|
|
* [volume create](volume_create.md)
|
|
* [volume inspect](volume_inspect.md)
|
|
* [volume ls](volume_ls.md)
|
|
* [Understand Data Volumes](../../tutorials/dockervolumes.md)
|