From ff9f0134aefbee1d3d757454f42e8dd99afb528e Mon Sep 17 00:00:00 2001 From: Kent Johnson Date: Mon, 20 Apr 2015 13:46:55 -0600 Subject: [PATCH] Clarify data volume init with existing data Though I am not clear on the intent of the sentence if it means that existing data in the base image is copied into the new volume then the additions I propose make that more clear than the present language. Signed-off-by: Kent Johnson --- docs/sources/userguide/dockervolumes.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/sources/userguide/dockervolumes.md b/docs/sources/userguide/dockervolumes.md index c319ecee5c..e80483fc2f 100644 --- a/docs/sources/userguide/dockervolumes.md +++ b/docs/sources/userguide/dockervolumes.md @@ -25,8 +25,8 @@ System*](/terms/layer/#union-file-system). Data volumes provide several useful features for persistent or shared data: - Volumes are initialized when a container is created. If the container's - base image contains data at the specified mount point, that data is - copied into the new volume. + base image contains data at the specified mount point, that existing data is + copied into the new volume upon volume initialization. - Data volumes can be shared and reused among containers. - Changes to a data volume are made directly. - Changes to a data volume will not be included when you update an image.