Merge pull request #16009 from azurezk/vol-create-conflict-option

volume create error on conflict option
Upstream-commit: df79536769eab04a7f1c618f9a390b36be6c53be
Component: engine
This commit is contained in:
Jess Frazelle
2015-10-12 15:27:36 -07:00
4 changed files with 37 additions and 0 deletions

View File

@ -29,6 +29,14 @@ The mount is created inside the container's `/src` directory. Docker does not su
Multiple containers can use the same volume in the same time period. This is useful if two containers need access to shared data. For example, if one container writes and the other reads the data.
Volume names must be unique among drivers. This means you cannot use the same volume name with two different drivers. If you attempt this `docker` returns an error:
```
A volume named %s already exists with the %s driver. Choose a different volume name.
```
If you specify a volume name already in use on the current driver, Docker assumes you want to re-use the existing volume and does not return an error.
## Driver specific options
Some volume drivers may take options to customize the volume creation. Use the `-o` or `--opt` flags to pass driver options: