Browse code

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

Signed-off-by: Ben Firshman <ben@firshman.co.uk>

Ben Firshman authored on 2015/11/11 00:25:53
Showing 4 changed files
... ...
@@ -83,6 +83,7 @@ Creates a new container.
83 83
                                     If 'host-src' is missing, then docker creates a new volume.
84 84
                                     If neither 'rw' or 'ro' is specified then the volume is mounted
85 85
                                     in read-write mode.
86
+      --volume-driver=""            Optional volume driver for the container
86 87
       --volumes-from=[]             Mount volumes from the specified container(s)
87 88
       -w, --workdir=""              Working directory inside the container
88 89
 
... ...
@@ -84,6 +84,7 @@ parent = "smn_cli"
84 84
                                     If 'host-src' is missing, then docker creates a new volume.
85 85
                                     If neither 'rw' or 'ro' is specified then the volume is mounted
86 86
                                     in read-write mode.
87
+      --volume-driver=""            Optional volume driver for the container
87 88
       --volumes-from=[]             Mount volumes from the specified container(s)
88 89
       -w, --workdir=""              Working directory inside the container
89 90
 
... ...
@@ -63,6 +63,7 @@ docker-create - Create a new container
63 63
 [**--ulimit**[=*[]*]]
64 64
 [**--uts**[=*[]*]]
65 65
 [**-v**|**--volume**[=*[]*]]
66
+[**--volume-driver**[=*DRIVER*]]
66 67
 [**--volumes-from**[=*[]*]]
67 68
 [**-w**|**--workdir**[=*WORKDIR*]]
68 69
 IMAGE [COMMAND] [ARG...]
... ...
@@ -305,6 +306,13 @@ any options, the systems uses the following options:
305 305
 **-v**, **--volume**=[]
306 306
    Bind mount a volume (e.g., from the host: -v /host:/container, from Docker: -v /container)
307 307
 
308
+**--volume-driver**=""
309
+   Optional volume driver for the container
310
+
311
+   If the container has a volume either from the `VOLUME` instruction in a
312
+   Dockerfile or the `-v` flag, a driver can be specified to create the volumes
313
+   with. See **docker-volume-create(1)** for full details.
314
+
308 315
 **--volumes-from**=[]
309 316
    Mount volumes from the specified container(s)
310 317
 
... ...
@@ -63,9 +63,10 @@ docker-run - Run a command in a new container
63 63
 [**-t**|**--tty**[=*false*]]
64 64
 [**--tmpfs**[=*[CONTAINER-DIR[:<OPTIONS>]*]]
65 65
 [**-u**|**--user**[=*USER*]]
66
-[**-v**|**--volume**[=*[]*]]
67 66
 [**--ulimit**[=*[]*]]
68 67
 [**--uts**[=*[]*]]
68
+[**-v**|**--volume**[=*[]*]]
69
+[**--volume-driver**[=*DRIVER*]]
69 70
 [**--volumes-from**[=*[]*]]
70 71
 [**-w**|**--workdir**[=*WORKDIR*]]
71 72
 IMAGE [COMMAND] [ARG...]
... ...
@@ -512,6 +513,13 @@ For example, you can specify either `/foo` or `foo` for a `host-dir` value.
512 512
 If you supply the `/foo` value, Docker creates a bind-mount. If you supply
513 513
 the `foo` specification, Docker creates a named volume.
514 514
 
515
+**--volume-driver**=""
516
+   Optional volume driver for the container
517
+
518
+   If the container has a volume either from the `VOLUME` instruction in a
519
+   Dockerfile or the `-v` flag, a driver can be specified to create the volumes
520
+   with. See **docker-volume-create(1)** for full details.
521
+
515 522
 **--volumes-from**=[]
516 523
    Mount volumes from the specified container(s)
517 524