|
@@ -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)
|
|
|
|