From 431506329f3e9cac1edaed0452e2ac7daba4fd7b Mon Sep 17 00:00:00 2001 From: Peter Salvatore Date: Thu, 28 Aug 2014 16:41:17 -0400 Subject: [PATCH] Be more explicit about volume removal Signed-off-by: Peter Salvatore Upstream-commit: bfa3d5fa726dc27e44208b51557edca9b64cf4e9 Component: engine --- components/engine/docs/sources/userguide/dockervolumes.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/components/engine/docs/sources/userguide/dockervolumes.md b/components/engine/docs/sources/userguide/dockervolumes.md index 97593a1e04..02dd344ffc 100644 --- a/components/engine/docs/sources/userguide/dockervolumes.md +++ b/components/engine/docs/sources/userguide/dockervolumes.md @@ -119,7 +119,8 @@ You can also extend the chain by mounting the volume that came from the If you remove containers that mount volumes, including the initial `dbdata` container, or the subsequent containers `db1` and `db2`, the volumes will not -be deleted until there are no containers still referencing those volumes. This +be deleted. To delete the volume from disk, you must explicitly call +`docker rm -v` against the last container with a reference to the volume. This allows you to upgrade, or effectively migrate data volumes between containers. ## Backup, restore, or migrate data volumes