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

Merge pull request #6639 from leeplay/userguide

Browse Source 
Update dockervolumes.md
Upstream-commit: d3fde633bdc675a7a4cac8d0519e4cd96b69a03a
Component: engine
This commit is contained in:
Sven Dowideit
2014-06-26 09:19:34 +10:00
parent c959443de4 c16ee9f478
commit 03a05388ef
1 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@ -80,15 +80,15 @@ it.
Let's create a new named container with a volume to share.
$ docker run -d -v /dbdata --name dbdata training/postgres
$ sudo docker run -d -v /dbdata --name dbdata training/postgres
You can then use the `--volumes-from` flag to mount the `/dbdata` volume in another container.
$ docker run -d --volumes-from dbdata --name db1 training/postgres
$ sudo docker run -d --volumes-from dbdata --name db1 training/postgres
And another:
$ docker run -d --volumes-from dbdata --name db2 training/postgres
$ sudo docker run -d --volumes-from dbdata --name db2 training/postgres
You can use multiple `--volumes-from` parameters to bring together multiple data
volumes from multiple containers.
@ -96,7 +96,7 @@ volumes from multiple containers.
You can also extend the chain by mounting the volume that came from the
`dbdata` container in yet another container via the `db1` or `db2` containers.
$ docker run -d --name db3 --volumes-from db1 training/postgres
$ sudo docker run -d --name db3 --volumes-from db1 training/postgres
If you remove containers that mount volumes, including the initial `dbdata`
container, or the subsequent containers `db1` and `db2`, the volumes will not