@@ -12,7 +12,6 @@ func NewVolumeCommand(dockerCli *command.DockerCli) *cobra.Command {

 	cmd := &cobra.Command{

 		Use:   "volume COMMAND",

 		Short: "Manage volumes",

-		Long:  volumeDescription,

 		Args:  cli.NoArgs,

 		RunE:  dockerCli.ShowHelp,

 	}

@@ -25,21 +24,3 @@ func NewVolumeCommand(dockerCli *command.DockerCli) *cobra.Command {

 	)

 	return cmd

 }

-

-var volumeDescription = `

-The **docker volume** command has subcommands for managing data volumes. A data

-volume is a specially-designated directory that by-passes storage driver

-management.

-

-Data volumes persist data independent of a container's life cycle. When you

-delete a container, the Docker daemon does not delete any data volumes. You can

-share volumes across multiple containers. Moreover, you can share data volumes

-with other computing resources in your system.

-

-To see help for a subcommand, use:

-

-    docker volume COMMAND --help

-

-For full details on using docker volume visit Docker's online documentation.

-

-`

@@ -29,7 +29,6 @@ func newCreateCommand(dockerCli *command.DockerCli) *cobra.Command {

 	cmd := &cobra.Command{

 		Use:   "create [OPTIONS] [VOLUME]",

 		Short: "Create a volume",

-		Long:  createDescription,

 		Args:  cli.RequiresMaxArgs(1),

 		RunE: func(cmd *cobra.Command, args []string) error {

 			if len(args) == 1 {

@@ -70,42 +69,3 @@ func runCreate(dockerCli *command.DockerCli, opts createOptions) error {

 	fmt.Fprintf(dockerCli.Out(), "%s\n", vol.Name)

 	return nil

 }

-

-var createDescription = `

-Creates a new volume that containers can consume and store data in. If a name

-is not specified, Docker generates a random name. You create a volume and then

-configure the container to use it, for example:

-

-    $ docker volume create hello

-    hello

-    $ docker run -d -v hello:/world busybox ls /world

-

-The mount is created inside the container's **/src** directory. Docker doesn't

-not support relative paths for mount points inside the container.

-

-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.

-

-## Driver specific options

-

-Some volume drivers may take options to customize the volume creation. Use the

-**-o** or **--opt** flags to pass driver options:

-

-    $ docker volume create --driver fake --opt tardis=blue --opt timey=wimey

-

-These options are passed directly to the volume driver. Options for different

-volume drivers may do different things (or nothing at all).

-

-The built-in **local** driver on Windows does not support any options.

-

-The built-in **local** driver on Linux accepts options similar to the linux

-**mount** command:

-

-    $ docker volume create --driver local --opt type=tmpfs --opt device=tmpfs --opt o=size=100m,uid=1000

-

-Another example:

-

-    $ docker volume create --driver local --opt type=btrfs --opt device=/dev/sda2

-

-`

@@ -20,7 +20,6 @@ func newInspectCommand(dockerCli *command.DockerCli) *cobra.Command {

 	cmd := &cobra.Command{

 		Use:   "inspect [OPTIONS] VOLUME [VOLUME...]",

 		Short: "Display detailed information on one or more volumes",

-		Long:  inspectDescription,

 		Args:  cli.RequiresMinArgs(1),

 		RunE: func(cmd *cobra.Command, args []string) error {

 			opts.names = args

@@ -45,11 +44,3 @@ func runInspect(dockerCli *command.DockerCli, opts inspectOptions) error {

 	return inspect.Inspect(dockerCli.Out(), opts.names, opts.format, getVolFunc)

 }

-

-var inspectDescription = `

-Returns information about one or more volumes. By default, this command renders

-all results in a JSON array. You can specify an alternate format to execute a

-given template is executed for each result. Go's https://golang.org/pkg/text/template/

-package describes all the details of the format.

-

-`

@@ -34,7 +34,6 @@ func newListCommand(dockerCli *command.DockerCli) *cobra.Command {

 		Use:     "ls [OPTIONS]",

 		Aliases: []string{"list"},

 		Short:   "List volumes",

-		Long:    listDescription,

 		Args:    cli.NoArgs,

 		RunE: func(cmd *cobra.Command, args []string) error {

 			return runList(dockerCli, opts)

@@ -73,19 +72,3 @@ func runList(dockerCli *command.DockerCli, opts listOptions) error {

 	}

 	return formatter.VolumeWrite(volumeCtx, volumes.Volumes)

 }

-

-var listDescription = `

-

-Lists all the volumes Docker manages. You can filter using the **-f** or

-**--filter** flag. The filtering format is a **key=value** pair. To specify

-more than one filter,  pass multiple flags (for example,

-**--filter "foo=bar" --filter "bif=baz"**)

-

-The currently supported filters are:

-

-* **dangling** (boolean - **true** or **false**, **1** or **0**)

-* **driver** (a volume driver's name)

-* **label** (**label=<key>** or **label=<key>=<value>**)

-* **name** (a volume's name)

-

-`

deleted file mode 100644

@@ -1,99 +0,0 @@

-% DOCKER(1) Docker User Manuals

-% Docker Community

-% JUNE 2014

-# NAME

-docker-attach - Attach to a running container

-

-# SYNOPSIS

-**docker attach**

-[**--detach-keys**[=*[]*]]

-[**--help**]

-[**--no-stdin**]

-[**--sig-proxy**[=*true*]]

-CONTAINER

-

-# DESCRIPTION

-The **docker attach** command allows you to attach to a running container using

-the container's ID or name, either to view its ongoing output or to control it

-interactively.  You can attach to the same contained process multiple times

-simultaneously, screen sharing style, or quickly view the progress of your

-detached process.

-

-To stop a container, use `CTRL-c`. This key sequence sends `SIGKILL` to the

-container. You can detach from the container (and leave it running) using a

-configurable key sequence. The default sequence is `CTRL-p CTRL-q`. You

-configure the key sequence using the **--detach-keys** option or a configuration

-file. See **config-json(5)** for documentation on using a configuration file.

-

-It is forbidden to redirect the standard input of a `docker attach` command while

-attaching to a tty-enabled container (i.e.: launched with `-t`).

-

-# OPTIONS

-**--detach-keys**=""

-    Override the key sequence for detaching a container. Format is a single character `[a-Z]` or `ctrl-<value>` where `<value>` is one of: `a-z`, `@`, `^`, `[`, `,` or `_`.

-

-**--help**

-  Print usage statement

-

-**--no-stdin**=*true*|*false*

-   Do not attach STDIN. The default is *false*.

-

-**--sig-proxy**=*true*|*false*

-   Proxy all received signals to the process (non-TTY mode only). SIGCHLD, SIGKILL, and SIGSTOP are not proxied. The default is *true*.

-

-# Override the detach sequence

-

-If you want, you can configure an override the Docker key sequence for detach.

-This is useful if the Docker default sequence conflicts with key sequence you

-use for other applications. There are two ways to define your own detach key

-sequence, as a per-container override or as a configuration property on  your

-entire configuration.

-

-To override the sequence for an individual container, use the

-`--detach-keys="<sequence>"` flag with the `docker attach` command. The format of

-the `<sequence>` is either a letter [a-Z], or the `ctrl-` combined with any of

-the following:

-

-* `a-z` (a single lowercase alpha character )

-* `@` (at sign)

-* `[` (left bracket)

-* `\\` (two backward slashes)

-*  `_` (underscore)

-* `^` (caret)

-

-These `a`, `ctrl-a`, `X`, or `ctrl-\\` values are all examples of valid key

-sequences. To configure a different configuration default key sequence for all

-containers, see **docker(1)**.

-

-# EXAMPLES

-

-## Attaching to a container

-

-In this example the top command is run inside a container, from an image called

-fedora, in detached mode. The ID from the container is passed into the **docker

-attach** command:

-

-    # ID=$(sudo docker run -d fedora /usr/bin/top -b)

-    # sudo docker attach $ID

-    top - 02:05:52 up  3:05,  0 users,  load average: 0.01, 0.02, 0.05

-    Tasks:   1 total,   1 running,   0 sleeping,   0 stopped,   0 zombie

-    Cpu(s):  0.1%us,  0.2%sy,  0.0%ni, 99.7%id,  0.0%wa,  0.0%hi,  0.0%si,  0.0%st

-    Mem:    373572k total,   355560k used,    18012k free,    27872k buffers

-    Swap:   786428k total,        0k used,   786428k free,   221740k cached

-

-    PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND

-    1 root      20   0 17200 1116  912 R    0  0.3   0:00.03 top

-

-    top - 02:05:55 up  3:05,  0 users,  load average: 0.01, 0.02, 0.05

-    Tasks:   1 total,   1 running,   0 sleeping,   0 stopped,   0 zombie

-    Cpu(s):  0.0%us,  0.2%sy,  0.0%ni, 99.8%id,  0.0%wa,  0.0%hi,  0.0%si,  0.0%st

-    Mem:    373572k total,   355244k used,    18328k free,    27872k buffers

-    Swap:   786428k total,        0k used,   786428k free,   221776k cached

-

-    PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND

-    1 root      20   0 17208 1144  932 R    0  0.3   0:00.03 top

-

-# HISTORY

-April 2014, Originally compiled by William Henry (whenry at redhat dot com)

-based on docker.com source material and internal work.

-June 2014, updated by Sven Dowideit <SvenDowideit@home.org.au>

deleted file mode 100644

@@ -1,71 +0,0 @@

-% DOCKER(1) Docker User Manuals

-% Docker Community

-% JUNE 2014

-# NAME

-docker-commit - Create a new image from a container's changes

-

-# SYNOPSIS

-**docker commit**

-[**-a**|**--author**[=*AUTHOR*]]

-[**-c**|**--change**[=\[*DOCKERFILE INSTRUCTIONS*\]]]

-[**--help**]

-[**-m**|**--message**[=*MESSAGE*]]

-[**-p**|**--pause**[=*true*]]

-CONTAINER [REPOSITORY[:TAG]]

-

-# DESCRIPTION

-Create a new image from an existing container specified by name or

-container ID.  The new image will contain the contents of the

-container filesystem, *excluding* any data volumes. Refer to **docker-tag(1)**

-for more information about valid image and tag names.

-

-While the `docker commit` command is a convenient way of extending an

-existing image, you should prefer the use of a Dockerfile and `docker

-build` for generating images that you intend to share with other

-people.

-

-# OPTIONS

-**-a**, **--author**=""

-   Author (e.g., "John Hannibal Smith <hannibal@a-team.com>")

-

-**-c** , **--change**=[]

-   Apply specified Dockerfile instructions while committing the image

-   Supported Dockerfile instructions: `CMD`|`ENTRYPOINT`|`ENV`|`EXPOSE`|`LABEL`|`ONBUILD`|`USER`|`VOLUME`|`WORKDIR`

-

-**--help**

-  Print usage statement

-

-**-m**, **--message**=""

-   Commit message

-

-**-p**, **--pause**=*true*|*false*

-   Pause container during commit. The default is *true*.

-

-# EXAMPLES

-

-## Creating a new image from an existing container

-An existing Fedora based container has had Apache installed while running

-in interactive mode with the bash shell. Apache is also running. To

-create a new image run `docker ps` to find the container's ID and then run:

-

-    # docker commit -m="Added Apache to Fedora base image" \

-      -a="A D Ministrator" 98bd7fc99854 fedora/fedora_httpd:20

-

-Note that only a-z0-9-_. are allowed when naming images from an 

-existing container.

-

-## Apply specified Dockerfile instructions while committing the image

-If an existing container was created without the DEBUG environment

-variable set to "true", you can create a new image based on that

-container by first getting the container's ID with `docker ps` and

-then running:

-

-    # docker commit -c="ENV DEBUG true" 98bd7fc99854 debug-image

-

-# HISTORY

-April 2014, Originally compiled by William Henry (whenry at redhat dot com)

-based on docker.com source material and in

-June 2014, updated by Sven Dowideit <SvenDowideit@home.org.au>

-July 2014, updated by Sven Dowideit <SvenDowideit@home.org.au>

-Oct 2014, updated by Daniel, Dao Quang Minh <daniel at nitrous dot io>

-June 2015, updated by Sally O'Malley <somalley@redhat.com>

deleted file mode 100644

@@ -1,175 +0,0 @@

-% DOCKER(1) Docker User Manuals

-% Docker Community

-% JUNE 2014

-# NAME

-docker-cp - Copy files/folders between a container and the local filesystem.

-

-# SYNOPSIS

-**docker cp**

-[**--help**]

-CONTAINER:SRC_PATH DEST_PATH|-

-

-**docker cp**

-[**--help**]

-SRC_PATH|- CONTAINER:DEST_PATH

-

-# DESCRIPTION

-

-The `docker cp` utility copies the contents of `SRC_PATH` to the `DEST_PATH`.

-You can copy from the container's file system to the local machine or the

-reverse, from the local filesystem to the container. If `-` is specified for

-either the `SRC_PATH` or `DEST_PATH`, you can also stream a tar archive from

-`STDIN` or to `STDOUT`. The `CONTAINER` can be a running or stopped container.

-The `SRC_PATH` or `DEST_PATH` can be a file or directory.

-

-The `docker cp` command assumes container paths are relative to the container's 

-`/` (root) directory. This means supplying the initial forward slash is optional; 

-The command sees `compassionate_darwin:/tmp/foo/myfile.txt` and

-`compassionate_darwin:tmp/foo/myfile.txt` as identical. Local machine paths can

-be an absolute or relative value. The command interprets a local machine's

-relative paths as relative to the current working directory where `docker cp` is

-run.

-

-The `cp` command behaves like the Unix `cp -a` command in that directories are

-copied recursively with permissions preserved if possible. Ownership is set to

-the user and primary group at the destination. For example, files copied to a

-container are created with `UID:GID` of the root user. Files copied to the local

-machine are created with the `UID:GID` of the user which invoked the `docker cp`

-command.  If you specify the `-L` option, `docker cp` follows any symbolic link

-in the `SRC_PATH`. `docker cp` does *not* create parent directories for

-`DEST_PATH` if they do not exist.

-

-Assuming a path separator of `/`, a first argument of `SRC_PATH` and second

-argument of `DEST_PATH`, the behavior is as follows:

-

-- `SRC_PATH` specifies a file

-    - `DEST_PATH` does not exist

-        - the file is saved to a file created at `DEST_PATH`

-    - `DEST_PATH` does not exist and ends with `/`

-        - Error condition: the destination directory must exist.

-    - `DEST_PATH` exists and is a file

-        - the destination is overwritten with the source file's contents

-    - `DEST_PATH` exists and is a directory

-        - the file is copied into this directory using the basename from

-          `SRC_PATH`

-- `SRC_PATH` specifies a directory

-    - `DEST_PATH` does not exist

-        - `DEST_PATH` is created as a directory and the *contents* of the source

-           directory are copied into this directory

-    - `DEST_PATH` exists and is a file

-        - Error condition: cannot copy a directory to a file

-    - `DEST_PATH` exists and is a directory

-        - `SRC_PATH` does not end with `/.`

-            - the source directory is copied into this directory

-        - `SRC_PATH` does end with `/.`

-            - the *content* of the source directory is copied into this

-              directory

-

-The command requires `SRC_PATH` and `DEST_PATH` to exist according to the above

-rules. If `SRC_PATH` is local and is a symbolic link, the symbolic link, not

-the target, is copied by default. To copy the link target and not the link, 

-specify the `-L` option.

-

-A colon (`:`) is used as a delimiter between `CONTAINER` and its path. You can

-also use `:` when specifying paths to a `SRC_PATH` or `DEST_PATH` on a local

-machine, for example  `file:name.txt`. If you use a `:` in a local machine path,

-you must be explicit with a relative or absolute path, for example:

-

-    `/path/to/file:name.txt` or `./file:name.txt`

-

-It is not possible to copy certain system files such as resources under

-`/proc`, `/sys`, `/dev`, tmpfs, and mounts created by the user in the container.

-However, you can still copy such files by manually running `tar` in `docker exec`.

-For example (consider `SRC_PATH` and `DEST_PATH` are directories):

-

-    $ docker exec foo tar Ccf $(dirname SRC_PATH) - $(basename SRC_PATH) | tar Cxf DEST_PATH -

-

-or

-

-    $ tar Ccf $(dirname SRC_PATH) - $(basename SRC_PATH) | docker exec -i foo tar Cxf DEST_PATH -

-

-

-Using `-` as the `SRC_PATH` streams the contents of `STDIN` as a tar archive.

-The command extracts the content of the tar to the `DEST_PATH` in container's

-filesystem. In this case, `DEST_PATH` must specify a directory. Using `-` as

-the `DEST_PATH` streams the contents of the resource as a tar archive to `STDOUT`.

-

-# OPTIONS

-**-L**, **--follow-link**=*true*|*false*

-  Follow symbol link in SRC_PATH

-

-**--help**

-  Print usage statement

-

-# EXAMPLES

-

-Suppose a container has finished producing some output as a file it saves

-to somewhere in its filesystem. This could be the output of a build job or

-some other computation. You can copy these outputs from the container to a

-location on your local host.

-

-If you want to copy the `/tmp/foo` directory from a container to the

-existing `/tmp` directory on your host. If you run `docker cp` in your `~`

-(home) directory on the local host:

-

-    $ docker cp compassionate_darwin:tmp/foo /tmp

-

-Docker creates a `/tmp/foo` directory on your host. Alternatively, you can omit

-the leading slash in the command. If you execute this command from your home

-directory:

-

-    $ docker cp compassionate_darwin:tmp/foo tmp

-

-If `~/tmp` does not exist, Docker will create it and copy the contents of

-`/tmp/foo` from the container into this new directory. If `~/tmp` already

-exists as a directory, then Docker will copy the contents of `/tmp/foo` from

-the container into a directory at `~/tmp/foo`.

-

-When copying a single file to an existing `LOCALPATH`, the `docker cp` command

-will either overwrite the contents of `LOCALPATH` if it is a file or place it

-into `LOCALPATH` if it is a directory, overwriting an existing file of the same

-name if one exists. For example, this command:

-

-    $ docker cp sharp_ptolemy:/tmp/foo/myfile.txt /test

-

-If `/test` does not exist on the local machine, it will be created as a file

-with the contents of `/tmp/foo/myfile.txt` from the container. If `/test`

-exists as a file, it will be overwritten. Lastly, if `/test` exists as a

-directory, the file will be copied to `/test/myfile.txt`.

-

-Next, suppose you want to copy a file or folder into a container. For example,

-this could be a configuration file or some other input to a long running

-computation that you would like to place into a created container before it

-starts. This is useful because it does not require the configuration file or

-other input to exist in the container image.

-

-If you have a file, `config.yml`, in the current directory on your local host

-and wish to copy it to an existing directory at `/etc/my-app.d` in a container,

-this command can be used:

-

-    $ docker cp config.yml myappcontainer:/etc/my-app.d

-

-If you have several files in a local directory `/config` which you need to copy

-to a directory `/etc/my-app.d` in a container:

-

-    $ docker cp /config/. myappcontainer:/etc/my-app.d

-

-The above command will copy the contents of the local `/config` directory into

-the directory `/etc/my-app.d` in the container.

-

-Finally, if you want to copy a symbolic link into a container, you typically

-want to  copy the linked target and not the link itself. To copy the target, use

-the `-L` option, for example:

-

-    $ ln -s /tmp/somefile /tmp/somefile.ln

-    $ docker cp -L /tmp/somefile.ln myappcontainer:/tmp/

-

-This command copies content of the local `/tmp/somefile` into the file

-`/tmp/somefile.ln` in the container. Without `-L` option, the `/tmp/somefile.ln`

-preserves its symbolic link but not its content.

-

-# HISTORY

-April 2014, Originally compiled by William Henry (whenry at redhat dot com)

-based on docker.com source material and internal work.

-June 2014, updated by Sven Dowideit <SvenDowideit@home.org.au>

-May 2015, updated by Josh Hawn <josh.hawn@docker.com>

deleted file mode 100644

@@ -1,553 +0,0 @@

-% DOCKER(1) Docker User Manuals

-% Docker Community

-% JUNE 2014

-# NAME

-docker-create - Create a new container

-

-# SYNOPSIS

-**docker create**

-[**-a**|**--attach**[=*[]*]]

-[**--add-host**[=*[]*]]

-[**--blkio-weight**[=*[BLKIO-WEIGHT]*]]

-[**--blkio-weight-device**[=*[]*]]

-[**--cpu-shares**[=*0*]]

-[**--cap-add**[=*[]*]]

-[**--cap-drop**[=*[]*]]

-[**--cgroup-parent**[=*CGROUP-PATH*]]

-[**--cidfile**[=*CIDFILE*]]

-[**--cpu-count**[=*0*]]

-[**--cpu-percent**[=*0*]]

-[**--cpu-period**[=*0*]]

-[**--cpu-quota**[=*0*]]

-[**--cpu-rt-period**[=*0*]]

-[**--cpu-rt-runtime**[=*0*]]

-[**--cpus**[=*0.0*]]

-[**--cpuset-cpus**[=*CPUSET-CPUS*]]

-[**--cpuset-mems**[=*CPUSET-MEMS*]]

-[**--device**[=*[]*]]

-[**--device-read-bps**[=*[]*]]

-[**--device-read-iops**[=*[]*]]

-[**--device-write-bps**[=*[]*]]

-[**--device-write-iops**[=*[]*]]

-[**--dns**[=*[]*]]

-[**--dns-search**[=*[]*]]

-[**--dns-option**[=*[]*]]

-[**-e**|**--env**[=*[]*]]

-[**--entrypoint**[=*ENTRYPOINT*]]

-[**--env-file**[=*[]*]]

-[**--expose**[=*[]*]]

-[**--group-add**[=*[]*]]

-[**-h**|**--hostname**[=*HOSTNAME*]]

-[**--help**]

-[**-i**|**--interactive**]

-[**--ip**[=*IPv4-ADDRESS*]]

-[**--ip6**[=*IPv6-ADDRESS*]]

-[**--ipc**[=*IPC*]]

-[**--isolation**[=*default*]]

-[**--kernel-memory**[=*KERNEL-MEMORY*]]

-[**-l**|**--label**[=*[]*]]

-[**--label-file**[=*[]*]]

-[**--link**[=*[]*]]

-[**--link-local-ip**[=*[]*]]

-[**--log-driver**[=*[]*]]

-[**--log-opt**[=*[]*]]

-[**-m**|**--memory**[=*MEMORY*]]

-[**--mac-address**[=*MAC-ADDRESS*]]

-[**--memory-reservation**[=*MEMORY-RESERVATION*]]

-[**--memory-swap**[=*LIMIT*]]

-[**--memory-swappiness**[=*MEMORY-SWAPPINESS*]]

-[**--name**[=*NAME*]]

-[**--network-alias**[=*[]*]]

-[**--network**[=*"bridge"*]]

-[**--oom-kill-disable**]

-[**--oom-score-adj**[=*0*]]

-[**-P**|**--publish-all**]

-[**-p**|**--publish**[=*[]*]]

-[**--pid**[=*[PID]*]]

-[**--userns**[=*[]*]]

-[**--pids-limit**[=*PIDS_LIMIT*]]

-[**--privileged**]

-[**--read-only**]

-[**--restart**[=*RESTART*]]

-[**--rm**]

-[**--security-opt**[=*[]*]]

-[**--storage-opt**[=*[]*]]

-[**--stop-signal**[=*SIGNAL*]]

-[**--stop-timeout**[=*TIMEOUT*]]

-[**--shm-size**[=*[]*]]

-[**--sysctl**[=*[]*]]

-[**-t**|**--tty**]

-[**--tmpfs**[=*[CONTAINER-DIR[:<OPTIONS>]*]]

-[**-u**|**--user**[=*USER*]]

-[**--ulimit**[=*[]*]]

-[**--uts**[=*[]*]]

-[**-v**|**--volume**[=*[[HOST-DIR:]CONTAINER-DIR[:OPTIONS]]*]]

-[**--volume-driver**[=*DRIVER*]]

-[**--volumes-from**[=*[]*]]

-[**-w**|**--workdir**[=*WORKDIR*]]

-IMAGE [COMMAND] [ARG...]

-

-# DESCRIPTION

-

-Creates a writeable container layer over the specified image and prepares it for

-running the specified command. The container ID is then printed to STDOUT. This

-is similar to **docker run -d** except the container is never started. You can 

-then use the **docker start <container_id>** command to start the container at

-any point.

-

-The initial status of the container created with **docker create** is 'created'.

-

-# OPTIONS

-**-a**, **--attach**=[]

-   Attach to STDIN, STDOUT or STDERR.

-

-**--add-host**=[]

-   Add a custom host-to-IP mapping (host:ip)

-

-**--blkio-weight**=*0*

-   Block IO weight (relative weight) accepts a weight value between 10 and 1000.

-

-**--blkio-weight-device**=[]

-   Block IO weight (relative device weight, format: `DEVICE_NAME:WEIGHT`).

-

-**--cpu-shares**=*0*

-   CPU shares (relative weight)

-

-**--cap-add**=[]

-   Add Linux capabilities

-

-**--cap-drop**=[]

-   Drop Linux capabilities

-

-**--cgroup-parent**=""

-   Path to cgroups under which the cgroup for the container will be created. If the path is not absolute, the path is considered to be relative to the cgroups path of the init process. Cgroups will be created if they do not already exist.

-

-**--cidfile**=""

-   Write the container ID to the file

-

-**--cpu-count**=*0*

-    Limit the number of CPUs available for execution by the container.

-    

-    On Windows Server containers, this is approximated as a percentage of total CPU usage.

-

-    On Windows Server containers, the processor resource controls are mutually exclusive, the order of precedence is CPUCount first, then CPUShares, and CPUPercent last.

-

-**--cpu-percent**=*0*

-    Limit the percentage of CPU available for execution by a container running on a Windows daemon.

-

-    On Windows Server containers, the processor resource controls are mutually exclusive, the order of precedence is CPUCount first, then CPUShares, and CPUPercent last.

-

-**--cpu-period**=*0*

-    Limit the CPU CFS (Completely Fair Scheduler) period

-

-    Limit the container's CPU usage. This flag tell the kernel to restrict the container's CPU usage to the period you specify.

-

-**--cpuset-cpus**=""

-   CPUs in which to allow execution (0-3, 0,1)

-

-**--cpuset-mems**=""

-   Memory nodes (MEMs) in which to allow execution (0-3, 0,1). Only effective on NUMA systems.

-

-   If you have four memory nodes on your system (0-3), use `--cpuset-mems=0,1`

-then processes in your Docker container will only use memory from the first

-two memory nodes.

-

-**--cpu-quota**=*0*

-   Limit the CPU CFS (Completely Fair Scheduler) quota

-

-**--cpu-rt-period**=0

-   Limit the CPU real-time period in microseconds

-

-   Limit the container's Real Time CPU usage. This flag tell the kernel to restrict the container's Real Time CPU usage to the period you specify.

-

-**--cpu-rt-runtime**=0

-   Limit the CPU real-time runtime in microseconds

-

-   Limit the containers Real Time CPU usage. This flag tells the kernel to limit the amount of time in a given CPU period Real Time tasks may consume. Ex:

-   Period of 1,000,000us and Runtime of 950,000us means that this container could consume 95% of available CPU and leave the remaining 5% to normal priority tasks.

-

-   The sum of all runtimes across containers cannot exceed the amount allotted to the parent cgroup.

-

-**--cpus**=0.0

-   Number of CPUs. The default is *0.0*.

-

-**--device**=[]

-   Add a host device to the container (e.g. --device=/dev/sdc:/dev/xvdc:rwm)

-

-**--device-read-bps**=[]

-    Limit read rate (bytes per second) from a device (e.g. --device-read-bps=/dev/sda:1mb)

-

-**--device-read-iops**=[]

-    Limit read rate (IO per second) from a device (e.g. --device-read-iops=/dev/sda:1000)

-

-**--device-write-bps**=[]

-    Limit write rate (bytes per second) to a device (e.g. --device-write-bps=/dev/sda:1mb)

-

-**--device-write-iops**=[]

-    Limit write rate (IO per second) to a device (e.g. --device-write-iops=/dev/sda:1000)

-

-**--dns**=[]

-   Set custom DNS servers

-

-**--dns-option**=[]

-   Set custom DNS options

-

-**--dns-search**=[]

-   Set custom DNS search domains (Use --dns-search=. if you don't wish to set the search domain)

-

-**-e**, **--env**=[]

-   Set environment variables

-

-**--entrypoint**=""

-   Overwrite the default ENTRYPOINT of the image

-

-**--env-file**=[]

-   Read in a line-delimited file of environment variables

-

-**--expose**=[]

-   Expose a port or a range of ports (e.g. --expose=3300-3310) from the container without publishing it to your host

-

-**--group-add**=[]

-   Add additional groups to run as

-

-**-h**, **--hostname**=""

-   Container host name

-

-**--help**

-  Print usage statement

-

-**-i**, **--interactive**=*true*|*false*

-   Keep STDIN open even if not attached. The default is *false*.

-

-**--ip**=""

-   Sets the container's interface IPv4 address (e.g. 172.23.0.9)

-

-   It can only be used in conjunction with **--network** for user-defined networks

-

-**--ip6**=""

-   Sets the container's interface IPv6 address (e.g. 2001:db8::1b99)

-

-   It can only be used in conjunction with **--network** for user-defined networks

-

-**--ipc**=""

-   Default is to create a private IPC namespace (POSIX SysV IPC) for the container

-                               'container:<name|id>': reuses another container shared memory, semaphores and message queues

-                               'host': use the host shared memory,semaphores and message queues inside the container.  Note: the host mode gives the container full access to local shared memory and is therefore considered insecure.

-

-**--isolation**="*default*"

-   Isolation specifies the type of isolation technology used by containers. Note

-that the default on Windows server is `process`, and the default on Windows client

-is `hyperv`. Linux only supports `default`.

-

-**--kernel-memory**=""

-   Kernel memory limit (format: `<number>[<unit>]`, where unit = b, k, m or g)

-

-   Constrains the kernel memory available to a container. If a limit of 0

-is specified (not using `--kernel-memory`), the container's kernel memory

-is not limited. If you specify a limit, it may be rounded up to a multiple

-of the operating system's page size and the value can be very large,

-millions of trillions.

-

-**-l**, **--label**=[]

-   Adds metadata to a container (e.g., --label=com.example.key=value)

-

-**--label-file**=[]

-   Read labels from a file. Delimit each label with an EOL.

-

-**--link**=[]

-   Add link to another container in the form of <name or id>:alias or just

-   <name or id> in which case the alias will match the name.

-

-**--link-local-ip**=[]

-   Add one or more link-local IPv4/IPv6 addresses to the container's interface

-

-**--log-driver**="*json-file*|*syslog*|*journald*|*gelf*|*fluentd*|*awslogs*|*splunk*|*etwlogs*|*gcplogs*|*none*"

-  Logging driver for the container. Default is defined by daemon `--log-driver` flag.

-  **Warning**: the `docker logs` command works only for the `json-file` and

-  `journald` logging drivers.

-

-**--log-opt**=[]

-  Logging driver specific options.

-

-**-m**, **--memory**=""

-   Memory limit (format: <number>[<unit>], where unit = b, k, m or g)

-

-   Allows you to constrain the memory available to a container. If the host

-supports swap memory, then the **-m** memory setting can be larger than physical

-RAM. If a limit of 0 is specified (not using **-m**), the container's memory is

-not limited. The actual limit may be rounded up to a multiple of the operating

-system's page size (the value would be very large, that's millions of trillions).

-

-**--mac-address**=""

-   Container MAC address (e.g. 92:d0:c6:0a:29:33)

-

-**--memory-reservation**=""

-   Memory soft limit (format: <number>[<unit>], where unit = b, k, m or g)

-

-   After setting memory reservation, when the system detects memory contention

-or low memory, containers are forced to restrict their consumption to their

-reservation. So you should always set the value below **--memory**, otherwise the

-hard limit will take precedence. By default, memory reservation will be the same

-as memory limit.

-

-**--memory-swap**="LIMIT"

-   A limit value equal to memory plus swap. Must be used with the  **-m**

-(**--memory**) flag. The swap `LIMIT` should always be larger than **-m**

-(**--memory**) value.

-

-   The format of `LIMIT` is `<number>[<unit>]`. Unit can be `b` (bytes),

-`k` (kilobytes), `m` (megabytes), or `g` (gigabytes). If you don't specify a

-unit, `b` is used. Set LIMIT to `-1` to enable unlimited swap.

-

-**--memory-swappiness**=""

-   Tune a container's memory swappiness behavior. Accepts an integer between 0 and 100.

-

-**--name**=""

-   Assign a name to the container

-

-**--network**="*bridge*"

-   Set the Network mode for the container

-                               'bridge': create a network stack on the default Docker bridge

-                               'none': no networking

-                               'container:<name|id>': reuse another container's network stack

-                               'host': use the Docker host network stack.  Note: the host mode gives the container full access to local system services such as D-bus and is therefore considered insecure.

-                               '<network-name>|<network-id>': connect to a user-defined network

-

-**--network-alias**=[]

-   Add network-scoped alias for the container

-

-**--oom-kill-disable**=*true*|*false*

-	Whether to disable OOM Killer for the container or not.

-

-**--oom-score-adj**=""

-    Tune the host's OOM preferences for containers (accepts -1000 to 1000)

-

-**-P**, **--publish-all**=*true*|*false*

-   Publish all exposed ports to random ports on the host interfaces. The default is *false*.

-

-**-p**, **--publish**=[]

-   Publish a container's port, or a range of ports, to the host

-                               format: ip:hostPort:containerPort | ip::containerPort | hostPort:containerPort | containerPort

-                               Both hostPort and containerPort can be specified as a range of ports. 

-                               When specifying ranges for both, the number of container ports in the range must match the number of host ports in the range. (e.g., `-p 1234-1236:1234-1236/tcp`)

-                               (use 'docker port' to see the actual mapping)

-

-**--pid**=""

-   Set the PID mode for the container

-   Default is to create a private PID namespace for the container