moby/volume
Yong Tang 6c5c34d50d 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>
2016-08-18 18:01:25 -07:00
..
drivers delete a useless variable 2016-07-29 15:34:21 +08:00
local Add requested comments about old buggy behavior 2016-08-18 10:07:22 -04:00
store Add --force in docker volume rm to fix out-of-band volume driver deletion 2016-08-18 18:01:25 -07:00
testutils Add support for volume scopes 2016-06-05 15:37:15 -04:00
volume.go revendor engine-api 2016-08-16 14:16:12 -04:00
volume_copy.go Add explicit flags for volume cp/no-cp 2016-03-21 20:38:44 -04:00
volume_propagation_linux.go revendor engine-api 2016-08-16 14:16:12 -04:00
volume_propagation_linux_test.go Remove static errors from errors package. 2016-02-26 15:49:09 -05:00
volume_propagation_unsupported.go revendor engine-api 2016-08-16 14:16:12 -04:00
volume_test.go Windows: Remove TP4 support from test code 2016-04-11 15:36:31 -07:00
volume_unix.go revendor engine-api 2016-08-16 14:16:12 -04:00
volume_windows.go Windows: Support RO volumes 14350+ 2016-06-07 14:55:36 -07:00