From cf35f111d782f0207c453517f9772931f6a3959b Mon Sep 17 00:00:00 2001 From: Hong Xu Date: Fri, 6 Mar 2015 12:26:28 -0800 Subject: [PATCH] Update doc: specify a dummy command for "docker create" "docker create" for data containers should specify a dummy command to avoid accidential "docker start" to cause unexpected data loss. Signed-off-by: Hong Xu Upstream-commit: fb6fab83df5663eb76c8cd57e3845f58c9ee36b3 Component: engine --- components/engine/docs/sources/userguide/dockervolumes.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/components/engine/docs/sources/userguide/dockervolumes.md b/components/engine/docs/sources/userguide/dockervolumes.md index fcf7c55943..d533224656 100644 --- a/components/engine/docs/sources/userguide/dockervolumes.md +++ b/components/engine/docs/sources/userguide/dockervolumes.md @@ -124,7 +124,7 @@ Let's create a new named container with a volume to share. While this container doesn't run an application, it reuses the `training/postgres` image so that all containers are using layers in common, saving disk space. - $ sudo docker create -v /dbdata --name dbdata training/postgres + $ sudo docker create -v /dbdata --name dbdata training/postgres /bin/true You can then use the `--volumes-from` flag to mount the `/dbdata` volume in another container.