Browse Source

Add docs and man page entry for --volume-driver

Signed-off-by: Ben Firshman <ben@firshman.co.uk>
Ben Firshman 9 years ago
parent
commit
fe3ec3f77f

+ 1 - 0
docs/reference/commandline/create.md

@@ -83,6 +83,7 @@ Creates a new container.
                                     If 'host-src' is missing, then docker creates a new volume.
                                     If neither 'rw' or 'ro' is specified then the volume is mounted
                                     in read-write mode.
+      --volume-driver=""            Optional volume driver for the container
       --volumes-from=[]             Mount volumes from the specified container(s)
       -w, --workdir=""              Working directory inside the container
 

+ 1 - 0
docs/reference/commandline/run.md

@@ -84,6 +84,7 @@ parent = "smn_cli"
                                     If 'host-src' is missing, then docker creates a new volume.
                                     If neither 'rw' or 'ro' is specified then the volume is mounted
                                     in read-write mode.
+      --volume-driver=""            Optional volume driver for the container
       --volumes-from=[]             Mount volumes from the specified container(s)
       -w, --workdir=""              Working directory inside the container
 

+ 8 - 0
man/docker-create.1.md

@@ -63,6 +63,7 @@ docker-create - Create a new container
 [**--ulimit**[=*[]*]]
 [**--uts**[=*[]*]]
 [**-v**|**--volume**[=*[]*]]
+[**--volume-driver**[=*DRIVER*]]
 [**--volumes-from**[=*[]*]]
 [**-w**|**--workdir**[=*WORKDIR*]]
 IMAGE [COMMAND] [ARG...]
@@ -305,6 +306,13 @@ any options, the systems uses the following options:
 **-v**, **--volume**=[]
    Bind mount a volume (e.g., from the host: -v /host:/container, from Docker: -v /container)
 
+**--volume-driver**=""
+   Optional volume driver for the container
+
+   If the container has a volume either from the `VOLUME` instruction in a
+   Dockerfile or the `-v` flag, a driver can be specified to create the volumes
+   with. See **docker-volume-create(1)** for full details.
+
 **--volumes-from**=[]
    Mount volumes from the specified container(s)
 

+ 9 - 1
man/docker-run.1.md

@@ -63,9 +63,10 @@ docker-run - Run a command in a new container
 [**-t**|**--tty**[=*false*]]
 [**--tmpfs**[=*[CONTAINER-DIR[:<OPTIONS>]*]]
 [**-u**|**--user**[=*USER*]]
-[**-v**|**--volume**[=*[]*]]
 [**--ulimit**[=*[]*]]
 [**--uts**[=*[]*]]
+[**-v**|**--volume**[=*[]*]]
+[**--volume-driver**[=*DRIVER*]]
 [**--volumes-from**[=*[]*]]
 [**-w**|**--workdir**[=*WORKDIR*]]
 IMAGE [COMMAND] [ARG...]
@@ -512,6 +513,13 @@ For example, you can specify either `/foo` or `foo` for a `host-dir` value.
 If you supply the `/foo` value, Docker creates a bind-mount. If you supply
 the `foo` specification, Docker creates a named volume.
 
+**--volume-driver**=""
+   Optional volume driver for the container
+
+   If the container has a volume either from the `VOLUME` instruction in a
+   Dockerfile or the `-v` flag, a driver can be specified to create the volumes
+   with. See **docker-volume-create(1)** for full details.
+
 **--volumes-from**=[]
    Mount volumes from the specified container(s)