p4u1/docker-cli
0
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Be more explicit about volume removal

Browse Source 
Signed-off-by: Peter Salvatore <peter@psftw.com>
Upstream-commit: bfa3d5fa726dc27e44208b51557edca9b64cf4e9
Component: engine
This commit is contained in:
Peter Salvatore
2014-08-28 16:41:17 -04:00
parent 910efd9532
commit 431506329f
1 changed files with 2 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
components/engine/docs/sources/userguide/dockervolumes.md
View File

@ -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