From ef0275c66c420944dd3de4647d2d25b78f8f1b5a Mon Sep 17 00:00:00 2001 From: Mark West Date: Mon, 23 Mar 2015 20:16:40 -0700 Subject: [PATCH] RE: Issue #6114. Updated docs to reflect docker inpsect for volumes Signed-off-by: Mark West --- docs/sources/userguide/dockervolumes.md | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) diff --git a/docs/sources/userguide/dockervolumes.md b/docs/sources/userguide/dockervolumes.md index d533224656..af4a7297fb 100644 --- a/docs/sources/userguide/dockervolumes.md +++ b/docs/sources/userguide/dockervolumes.md @@ -52,6 +52,27 @@ This will create a new volume inside a container at `/webapp`. > You can also use the `VOLUME` instruction in a `Dockerfile` to add one or > more new volumes to any container created from that image. +### Locating a volume + +You can locate the volume on the host by utilizing the 'docker inspect' command. + + $ docker inspect web + +The output will provide details on the container configurations including the +volumes. The output should look something similar to the following: + + ... + "Volumes": { + "/webapp": "/var/lib/docker/volumes/fac362...80535" + }, + "VolumesRW": { + "/webapp": true + } + ... + +You will notice in the above 'Volumes' is specifying the location on the host and +'VolumesRW' is specifying that the volume is read/write. + ### Mount a Host Directory as a Data Volume In addition to creating a volume using the `-v` flag you can also mount a