docker
/
docs
mirror of https://github.com/docker/docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Cloudstor docs (#2520) 

* Clarify rg-name and rg-region are optional for EE

* fix cloudstor documentation to align with the plugin alias that is used
This commit is contained in:
Deep Debroy 2017-03-28 16:50:05 -07:00 committed by Misty Stanley-Jones
parent 783f19facc
commit d611a12ef0
2 changed files with 6 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
docker-for-aws/persistent-data-volumes.md
View File

@ -17,18 +17,16 @@ After creating a swarm on Docker for AWS and connecting to any manager using SSH
```bash
$ docker plugin ls
ID NAME DESCRIPTION ENABLED
f416c95c0dcc docker4x/cloudstor:aws-v{{ edition_version }} cloud storage plugin for Docker true
f416c95c0dcc cloudstor:aws cloud storage plugin for Docker true
```
**Note**: Make note of the plugin tag name, because it will change between versions, and yours may be different then listed here.
The following examples show how to create swarm services that require data persistence using the --mount flag and specifying Cloudstor as the driver.
### Share the same volume between tasks:
```bash
docker service create --replicas 5 --name ping1 \
--mount type=volume,volume-driver=docker4x/cloudstor:aws-v{{ edition_version }},source=sharedvol1,destination=/shareddata \
--mount type=volume,volume-driver=cloudstor:aws,source=sharedvol1,destination=/shareddata \
alpine ping docker.com
```
@ -41,7 +39,7 @@ With the above example, you can make sure that the volume is indeed shared by lo
```bash
{% raw %}
docker service create --replicas 5 --name ping2 \
--mount type=volume,volume-driver=docker4x/cloudstor:aws-v{{ edition_version }},source={{.Service.Name}}-{{.Task.Slot}}-vol,destination=/mydata \
--mount type=volume,volume-driver=cloudstor:aws,source={{.Service.Name}}-{{.Task.Slot}}-vol,destination=/mydata \
alpine ping docker.com
{% endraw %}
```

8
docker-for-azure/persistent-data-volumes.md
View File

@ -17,18 +17,16 @@ After creating a swarm on Docker for Azure and connecting to any manager using S
```bash
$ docker plugin ls
ID NAME DESCRIPTION ENABLED
f416c95c0dcc docker4x/cloudstor:azure-v{{ edition_version }} cloud storage plugin for Docker true
f416c95c0dcc cloudstor:azure cloud storage plugin for Docker true
```
**Note**: Make note of the plugin tag name, because it will change between versions, and yours may be different then listed here.
The following examples show how to create swarm services that require data persistence using the --mount flag and specifying Cloudstor as the driver.
### Share the same volume between tasks:
```bash
docker service create --replicas 5 --name ping1 \
--mount type=volume,volume-driver=docker4x/cloudstor:azure-v{{ edition_version }},source=sharedvol1,destination=/shareddata \
--mount type=volume,volume-driver=cloudstor:azure,source=sharedvol1,destination=/shareddata \
alpine ping docker.com
```
@ -41,7 +39,7 @@ With the above example, you can make sure that the volume is indeed shared by lo
```bash
{% raw %}
docker service create --replicas 5 --name ping2 \
--mount type=volume,volume-driver=docker4x/cloudstor:azure-v{{ edition_version }},source={{.Service.Name}}-{{.Task.Slot}}-vol,destination=/mydata \
--mount type=volume,volume-driver=cloudstor:azure,source={{.Service.Name}}-{{.Task.Slot}}-vol,destination=/mydata \
alpine ping docker.com
{% endraw %}
```