Add --force
in docker volume rm
to fix out-of-band volume driver deletion
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>
This commit is contained in:
parent
0c200d4894
commit
9a16c4fccd
@ -11,7 +11,7 @@ parent = "smn_cli"
|
|||||||
# volume rm
|
# volume rm
|
||||||
|
|
||||||
```markdown
|
```markdown
|
||||||
Usage: docker volume rm VOLUME [VOLUME...]
|
Usage: docker volume rm [OPTIONS] VOLUME [VOLUME...]
|
||||||
|
|
||||||
Remove one or more volumes
|
Remove one or more volumes
|
||||||
|
|
||||||
@ -19,6 +19,7 @@ Aliases:
|
|||||||
rm, remove
|
rm, remove
|
||||||
|
|
||||||
Options:
|
Options:
|
||||||
|
-f, --force Force the removal of one or more volumes
|
||||||
--help Print usage
|
--help Print usage
|
||||||
```
|
```
|
||||||
|
|
||||||
|
Loading…
x
Reference in New Issue
Block a user