.TH "DOCKER" "1" " Docker User Manuals" "Docker Community" "JUNE 2014"  ""

.SH NAME

.PP

docker\-create \- Create a new container

.SH SYNOPSIS

.PP

\fBdocker create\fP

[\fB\-a\fP|\fB\-\-attach\fP[=\fI[]\fP]]

[\fB\-\-add\-host\fP[=\fI[]\fP]]

[\fB\-\-blkio\-weight\fP[=\fI[BLKIO\-WEIGHT]\fP]]

[\fB\-\-blkio\-weight\-device\fP[=\fI[]\fP]]

[\fB\-\-cpu\-shares\fP[=\fI0\fP]]

[\fB\-\-cap\-add\fP[=\fI[]\fP]]

[\fB\-\-cap\-drop\fP[=\fI[]\fP]]

[\fB\-\-cgroup\-parent\fP[=\fICGROUP\-PATH\fP]]

[\fB\-\-cidfile\fP[=\fICIDFILE\fP]]

[\fB\-\-cpu\-period\fP[=\fI0\fP]]

[\fB\-\-cpu\-quota\fP[=\fI0\fP]]

[\fB\-\-cpuset\-cpus\fP[=\fICPUSET\-CPUS\fP]]

[\fB\-\-cpuset\-mems\fP[=\fICPUSET\-MEMS\fP]]

[\fB\-\-device\fP[=\fI[]\fP]]

[\fB\-\-device\-read\-bps\fP[=\fI[]\fP]]

[\fB\-\-device\-read\-iops\fP[=\fI[]\fP]]

[\fB\-\-device\-write\-bps\fP[=\fI[]\fP]]

[\fB\-\-device\-write\-iops\fP[=\fI[]\fP]]

[\fB\-\-dns\fP[=\fI[]\fP]]

[\fB\-\-dns\-search\fP[=\fI[]\fP]]

[\fB\-\-dns\-opt\fP[=\fI[]\fP]]

[\fB\-e\fP|\fB\-\-env\fP[=\fI[]\fP]]

[\fB\-\-entrypoint\fP[=\fIENTRYPOINT\fP]]

[\fB\-\-env\-file\fP[=\fI[]\fP]]

[\fB\-\-expose\fP[=\fI[]\fP]]

[\fB\-\-group\-add\fP[=\fI[]\fP]]

[\fB\-h\fP|\fB\-\-hostname\fP[=\fIHOSTNAME\fP]]

[\fB\-\-help\fP]

[\fB\-i\fP|\fB\-\-interactive\fP]

[\fB\-\-ip\fP[=\fIIPv4\-ADDRESS\fP]]

[\fB\-\-ip6\fP[=\fIIPv6\-ADDRESS\fP]]

[\fB\-\-ipc\fP[=\fIIPC\fP]]

[\fB\-\-isolation\fP[=\fIdefault\fP]]

[\fB\-\-kernel\-memory\fP[=\fIKERNEL\-MEMORY\fP]]

[\fB\-l\fP|\fB\-\-label\fP[=\fI[]\fP]]

[\fB\-\-label\-file\fP[=\fI[]\fP]]

[\fB\-\-link\fP[=\fI[]\fP]]

[\fB\-\-log\-driver\fP[=\fI[]\fP]]

[\fB\-\-log\-opt\fP[=\fI[]\fP]]

[\fB\-m\fP|\fB\-\-memory\fP[=\fIMEMORY\fP]]

[\fB\-\-mac\-address\fP[=\fIMAC\-ADDRESS\fP]]

[\fB\-\-memory\-reservation\fP[=\fIMEMORY\-RESERVATION\fP]]

[\fB\-\-memory\-swap\fP[=\fILIMIT\fP]]

[\fB\-\-memory\-swappiness\fP[=\fIMEMORY\-SWAPPINESS\fP]]

[\fB\-\-name\fP[=\fINAME\fP]]

[\fB\-\-net\fP[=\fI"bridge"\fP]]

[\fB\-\-net\-alias\fP[=\fI[]\fP]]

[\fB\-\-oom\-kill\-disable\fP]

[\fB\-\-oom\-score\-adj\fP[=\fI0\fP]]

[\fB\-P\fP|\fB\-\-publish\-all\fP]

[\fB\-p\fP|\fB\-\-publish\fP[=\fI[]\fP]]

[\fB\-\-pid\fP[=\fI[]\fP]]

[\fB\-\-privileged\fP]

[\fB\-\-read\-only\fP]

[\fB\-\-restart\fP[=\fIRESTART\fP]]

[\fB\-\-security\-opt\fP[=\fI[]\fP]]

[\fB\-\-stop\-signal\fP[=\fISIGNAL\fP]]

[\fB\-\-shm\-size\fP[=\fI[]\fP]]

[\fB\-t\fP|\fB\-\-tty\fP]

[\fB\-\-tmpfs\fP[=\fI[CONTAINER\-DIR[:<OPTIONS>]\fP]]

[\fB\-u\fP|\fB\-\-user\fP[=\fIUSER\fP]]

[\fB\-\-ulimit\fP[=\fI[]\fP]]

[\fB\-\-uts\fP[=\fI[]\fP]]

[\fB\-v\fP|\fB\-\-volume\fP[=\fI[[HOST\-DIR:]CONTAINER\-DIR[:OPTIONS]]\fP]]

[\fB\-\-volume\-driver\fP[=\fIDRIVER\fP]]

[\fB\-\-volumes\-from\fP[=\fI[]\fP]]

[\fB\-w\fP|\fB\-\-workdir\fP[=\fIWORKDIR\fP]]

IMAGE [COMMAND] [ARG...]

.SH DESCRIPTION

.PP

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 \fBdocker run \-d\fP except the container is never started. You can

then use the \fBdocker start <container_id>\fP command to start the container at

any point.

.PP

The initial status of the container created with \fBdocker create\fP is 'created'.

.SH OPTIONS

.PP

\fB\-a\fP, \fB\-\-attach\fP=[]

   Attach to STDIN, STDOUT or STDERR.

.PP

\fB\-\-add\-host\fP=[]

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

.PP

\fB\-\-blkio\-weight\fP=\fI0\fP

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

.PP

\fB\-\-blkio\-weight\-device\fP=[]

   Block IO weight (relative device weight, format: \fB\fCDEVICE\_NAME:WEIGHT\fR).

.PP

\fB\-\-cpu\-shares\fP=\fI0\fP

   CPU shares (relative weight)

.PP

\fB\-\-cap\-add\fP=[]

   Add Linux capabilities

.PP

\fB\-\-cap\-drop\fP=[]

   Drop Linux capabilities

.PP

\fB\-\-cgroup\-parent\fP=""

   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.

.PP

\fB\-\-cidfile\fP=""

   Write the container ID to the file

.PP

\fB\-\-cpu\-period\fP=\fI0\fP

    Limit the CPU CFS (Completely Fair Scheduler) period

.PP

\fB\-\-cpuset\-cpus\fP=""

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

.PP

\fB\-\-cpuset\-mems\fP=""

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

.PP

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

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

two memory nodes.

.PP

\fB\-\-cpu\-quota\fP=\fI0\fP

   Limit the CPU CFS (Completely Fair Scheduler) quota

.PP

\fB\-\-device\fP=[]

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

.PP

\fB\-\-device\-read\-bps\fP=[]

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

.PP

\fB\-\-device\-read\-iops\fP=[]

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

.PP

\fB\-\-device\-write\-bps\fP=[]

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

.PP

\fB\-\-device\-write\-iops\fP=[]

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

.PP

\fB\-\-dns\fP=[]

   Set custom DNS servers

.PP

\fB\-\-dns\-opt\fP=[]

   Set custom DNS options

.PP

\fB\-\-dns\-search\fP=[]

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

.PP

\fB\-e\fP, \fB\-\-env\fP=[]

   Set environment variables

.PP

\fB\-\-entrypoint\fP=""

   Overwrite the default ENTRYPOINT of the image

.PP

\fB\-\-env\-file\fP=[]

   Read in a line\-delimited file of environment variables

.PP

\fB\-\-expose\fP=[]

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

.PP

\fB\-\-group\-add\fP=[]

   Add additional groups to run as

.PP

\fB\-h\fP, \fB\-\-hostname\fP=""

   Container host name

.PP

\fB\-\-help\fP

  Print usage statement

.PP

\fB\-i\fP, \fB\-\-interactive\fP=\fItrue\fP|\fIfalse\fP

   Keep STDIN open even if not attached. The default is \fIfalse\fP.

.PP

\fB\-\-ip\fP=""

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

.PP

It can only be used in conjunction with \fB\-\-net\fP for user\-defined networks

.PP

\fB\-\-ip6\fP=""

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

.PP

It can only be used in conjunction with \fB\-\-net\fP for user\-defined networks

.PP

\fB\-\-ipc\fP=""

   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.

.PP

\fB\-\-isolation\fP="\fIdefault\fP"

   Isolation specifies the type of isolation technology used by containers.

.PP

\fB\-\-kernel\-memory\fP=""

   Kernel memory limit (format: \fB\fC<number>[<unit>]\fR, where unit = b, k, m or g)

.PP

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

is specified (not using \fB\fC\-\-kernel\-memory\fR), 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.

.PP

\fB\-l\fP, \fB\-\-label\fP=[]

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

.PP

\fB\-\-label\-file\fP=[]

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

.PP

\fB\-\-link\fP=[]

   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.

.PP

\fB\-\-log\-driver\fP="\fIjson\-file\fP|\fIsyslog\fP|\fIjournald\fP|\fIgelf\fP|\fIfluentd\fP|\fIawslogs\fP|\fIsplunk\fP|\fInone\fP"

  Logging driver for container. Default is defined by daemon \fB\fC\-\-log\-driver\fR flag.

  \fBWarning\fP: the \fB\fCdocker logs\fR command works only for the \fB\fCjson\-file\fR and

  \fB\fCjournald\fR logging drivers.

.PP

\fB\-\-log\-opt\fP=[]

  Logging driver specific options.

.PP

\fB\-m\fP, \fB\-\-memory\fP=""

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

.PP

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

supports swap memory, then the \fB\-m\fP memory setting can be larger than physical

RAM. If a limit of 0 is specified (not using \fB\-m\fP), 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).

.PP

\fB\-\-mac\-address\fP=""

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

.PP

\fB\-\-memory\-reservation\fP=""

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

.PP

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 \fB\-\-memory\fP, otherwise the

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

as memory limit.

.PP

\fB\-\-memory\-swap\fP="LIMIT"

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

(\fB\-\-memory\fP) flag. The swap \fB\fCLIMIT\fR should always be larger than \fB\-m\fP

(\fB\-\-memory\fP) value.

.PP

The format of \fB\fCLIMIT\fR is \fB\fC<number>[<unit>]\fR. Unit can be \fB\fCb\fR (bytes),

\fB\fCk\fR (kilobytes), \fB\fCm\fR (megabytes), or \fB\fCg\fR (gigabytes). If you don't specify a

unit, \fB\fCb\fR is used. Set LIMIT to \fB\fC\-1\fR to enable unlimited swap.

.PP

\fB\-\-memory\-swappiness\fP=""

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

.PP

\fB\-\-name\fP=""

   Assign a name to the container

.PP

\fB\-\-net\fP="\fIbridge\fP"

   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

.PP

\fB\-\-net\-alias\fP=[]

   Add network\-scoped alias for the container

.PP

\fB\-\-oom\-kill\-disable\fP=\fItrue\fP|\fIfalse\fP

    Whether to disable OOM Killer for the container or not.

.PP

\fB\-\-oom\-score\-adj\fP=""

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

.PP

\fB\-P\fP, \fB\-\-publish\-all\fP=\fItrue\fP|\fIfalse\fP

   Publish all exposed ports to random ports on the host interfaces. The default is \fIfalse\fP.

.PP

\fB\-p\fP, \fB\-\-publish\fP=[]

   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., \fB\fC\-p 1234\-1236:1234\-1236/tcp\fR)

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

.PP

\fB\-\-pid\fP=\fIhost\fP

   Set the PID mode for the container

     \fBhost\fP: use the host's PID namespace inside the container.

     Note: the host mode gives the container full access to local PID and is therefore considered insecure.

.PP

\fB\-\-privileged\fP=\fItrue\fP|\fIfalse\fP

   Give extended privileges to this container. The default is \fIfalse\fP.

.PP

\fB\-\-read\-only\fP=\fItrue\fP|\fIfalse\fP

   Mount the container's root filesystem as read only.

.PP

\fB\-\-restart\fP="\fIno\fP"

   Restart policy to apply when a container exits (no, on\-failure[:max\-retry], always, unless\-stopped).

.PP

\fB\-\-shm\-size\fP=""

   Size of \fB\fC/dev/shm\fR. The format is \fB\fC<number><unit>\fR. \fB\fCnumber\fR must be greater than \fB\fC0\fR.

   Unit is optional and can be \fB\fCb\fR (bytes), \fB\fCk\fR (kilobytes), \fB\fCm\fR (megabytes), or \fB\fCg\fR (gigabytes). If you omit the unit, the system uses bytes.

   If you omit the size entirely, the system uses \fB\fC64m\fR.

.PP

\fB\-\-security\-opt\fP=[]

   Security Options

.PP

\fB\-\-stop\-signal\fP=\fISIGTERM\fP

  Signal to stop a container. Default is SIGTERM.

.PP

\fB\-t\fP, \fB\-\-tty\fP=\fItrue\fP|\fIfalse\fP

   Allocate a pseudo\-TTY. The default is \fIfalse\fP.

.PP

\fB\-\-tmpfs\fP=[] Create a tmpfs mount

.PP

Mount a temporary filesystem (\fB\fCtmpfs\fR) mount into a container, for example:

.PP

$ docker run \-d \-\-tmpfs /tmp:rw,size=787448k,mode=1777 my\_image

.PP

This command mounts a \fB\fCtmpfs\fR at \fB\fC/tmp\fR within the container.  The supported mount

options are the same as the Linux default \fB\fCmount\fR flags. If you do not specify

any options, the systems uses the following options:

\fB\fCrw,noexec,nosuid,nodev,size=65536k\fR.

.PP

\fB\-u\fP, \fB\-\-user\fP=""

   Username or UID

.PP

\fB\-\-ulimit\fP=[]

   Ulimit options

.PP

\fB\-\-uts\fP=\fIhost\fP

   Set the UTS mode for the container

     \fBhost\fP: use the host's UTS namespace inside the container.

     Note: the host mode gives the container access to changing the host's hostname and is therefore considered insecure.

.PP

\fB\-v\fP|\fB\-\-volume\fP[=\fI[[HOST\-DIR:]CONTAINER\-DIR[:OPTIONS]]\fP]

   Create a bind mount. If you specify, \fB\fC\-v /HOST\-DIR:/CONTAINER\-DIR\fR, Docker

   bind mounts \fB\fC/HOST\-DIR\fR in the host to \fB\fC/CONTAINER\-DIR\fR in the Docker

   container. If 'HOST\-DIR' is omitted,  Docker automatically creates the new

   volume on the host.  The \fB\fCOPTIONS\fR are a comma delimited list and can be:

.IP \n+[step]

\item [rw|ro]

\item [z|Z]

\item [\fB\fC[r]shared\fR|\fB\fC[r]slave\fR|\fB\fC[r]private\fR]

.PP

The \fB\fCCONTAINER\-DIR\fR must be an absolute path such as \fB\fC/src/docs\fR. The \fB\fCHOST\-DIR\fR

can be an absolute path or a \fB\fCname\fR value. A \fB\fCname\fR value must start with an

alphanumeric character, followed by \fB\fCa\-z0\-9\fR, \fB\fC\_\fR (underscore), \fB\fC.\fR (period) or

\fB\fC\-\fR (hyphen). An absolute path starts with a \fB\fC/\fR (forward slash).

.PP

If you supply a \fB\fCHOST\-DIR\fR that is an absolute path,  Docker bind\-mounts to the

path you specify. If you supply a \fB\fCname\fR, Docker creates a named volume by that

\fB\fCname\fR. For example, you can specify either \fB\fC/foo\fR or \fB\fCfoo\fR for a \fB\fCHOST\-DIR\fR

value. If you supply the \fB\fC/foo\fR value, Docker creates a bind\-mount. If you

supply the \fB\fCfoo\fR specification, Docker creates a named volume.

.PP

You can specify multiple  \fB\-v\fP options to mount one or more mounts to a

container. To use these same mounts in other containers, specify the

\fB\-\-volumes\-from\fP option also.

.PP

You can add \fB\fC:ro\fR or \fB\fC:rw\fR suffix to a volume to mount it  read\-only or

read\-write mode, respectively. By default, the volumes are mounted read\-write.

See examples.

.PP

Labeling systems like SELinux require that proper labels are placed on volume

content mounted into a container. Without a label, the security system might

prevent the processes running inside the container from using the content. By

default, Docker does not change the labels set by the OS.

.PP

To change a label in the container context, you can add either of two suffixes

\fB\fC:z\fR or \fB\fC:Z\fR to the volume mount. These suffixes tell Docker to relabel file

objects on the shared volumes. The \fB\fCz\fR option tells Docker that two containers

share the volume content. As a result, Docker labels the content with a shared

content label. Shared volume labels allow all containers to read/write content.

The \fB\fCZ\fR option tells Docker to label the content with a private unshared label.

Only the current container can use a private volume.

.PP

By default bind mounted volumes are \fB\fCprivate\fR. That means any mounts done

inside container will not be visible on host and vice\-a\-versa. One can change

this behavior by specifying a volume mount propagation property. Making a

volume \fB\fCshared\fR mounts done under that volume inside container will be

visible on host and vice\-a\-versa. Making a volume \fB\fCslave\fR enables only one

way mount propagation and that is mounts done on host under that volume

will be visible inside container but not the other way around.

.PP

To control mount propagation property of volume one can use \fB\fC:[r]shared\fR,

\fB\fC:[r]slave\fR or \fB\fC:[r]private\fR propagation flag. Propagation property can

be specified only for bind mounted volumes and not for internal volumes or

named volumes. For mount propagation to work source mount point (mount point

where source dir is mounted on) has to have right propagation properties. For

shared volumes, source mount point has to be shared. And for slave volumes,

source mount has to be either shared or slave.

.PP

Use \fB\fCdf <source\-dir>\fR to figure out the source mount and then use

\fB\fCfindmnt \-o TARGET,PROPAGATION <source\-mount\-dir>\fR to figure out propagation

properties of source mount. If \fB\fCfindmnt\fR utility is not available, then one

can look at mount entry for source mount point in \fB\fC/proc/self/mountinfo\fR. Look

at \fB\fCoptional fields\fR and see if any propagaion properties are specified.

\fB\fCshared:X\fR means mount is \fB\fCshared\fR, \fB\fCmaster:X\fR means mount is \fB\fCslave\fR and if

nothing is there that means mount is \fB\fCprivate\fR.

.PP

To change propagation properties of a mount point use \fB\fCmount\fR command. For

example, if one wants to bind mount source directory \fB\fC/foo\fR one can do

\fB\fCmount \-\-bind /foo /foo\fR and \fB\fCmount \-\-make\-private \-\-make\-shared /foo\fR. This

will convert /foo into a \fB\fCshared\fR mount point. Alternatively one can directly

change propagation properties of source mount. Say \fB\fC/\fR is source mount for

\fB\fC/foo\fR, then use \fB\fCmount \-\-make\-shared /\fR to convert \fB\fC/\fR into a \fB\fCshared\fR mount.

.PP

.RS

.PP

\fBNote\fP:

When using systemd to manage the Docker daemon's start and stop, in the systemd

unit file there is an option to control mount propagation for the Docker daemon

itself, called \fB\fCMountFlags\fR. The value of this setting may cause Docker to not

see mount propagation changes made on the mount point. For example, if this value

is \fB\fCslave\fR, you may not be able to use the \fB\fCshared\fR or \fB\fCrshared\fR propagation on

a volume.

.RE

.PP

\fB\-\-volume\-driver\fP=""

   Container's volume driver. This driver creates volumes specified either from

   a Dockerfile's \fB\fCVOLUME\fR instruction or from the \fB\fCdocker run \-v\fR flag.

   See \fBdocker\-volume\-create(1)\fP for full details.

.PP

\fB\-\-volumes\-from\fP=[]

   Mount volumes from the specified container(s)

.PP

\fB\-w\fP, \fB\-\-workdir\fP=""

   Working directory inside the container

.SH EXAMPLES