2014-08-19 21:10:42 -04:00
% DOCKER(1) Docker User Manuals
% Docker Community
% JUNE 2014
# NAME
docker-create - Create a new container
# SYNOPSIS
**docker create**
[**-a**|**--attach**[=*[]*]]
2014-09-25 02:07:55 -04:00
[**--add-host**[=*[]*]]
2015-05-06 23:55:58 -04:00
[**--blkio-weight**[=*[BLKIO-WEIGHT]*]]
2014-08-19 21:10:42 -04:00
[**-c**|**--cpu-shares**[=*0*]]
[**--cap-add**[=*[]*]]
[**--cap-drop**[=*[]*]]
[**--cidfile**[=*CIDFILE*]]
2015-04-08 04:58:59 -04:00
[**--cpu-period**[=*0*]]
move resources from Config to HostConfig
Cgroup resources are host dependent, they should be in hostConfig.
For backward compatibility, we just copy it to hostConfig, and leave it in
Config for now, so there is no regressions, but the right way to use this
throught json is to put it in HostConfig, like:
{
"Hostname": "",
...
"HostConfig": {
"CpuShares": 512,
"Memory": 314572800,
...
}
}
As we will add CpusetMems, CpusetCpus is definitely a better name, but some
users are already using Cpuset in their http APIs, we also make it compatible.
The main idea is keep using Cpuset in Config Struct, and make it has the same
value as CpusetCpus, but not always, some scenarios:
- Users use --cpuset in docker command, it can setup cpuset.cpus and can
get Cpuset field from docker inspect or other http API which will get
config info.
- Users use --cpuset-cpus in docker command, ditto.
- Users use Cpuset field in their http APIs, ditto.
- Users use CpusetCpus field in their http APIs, they won't get Cpuset field
in Config info, because by then, they should already know what happens
to Cpuset.
Signed-off-by: Qiang Huang <h.huangqiang@huawei.com>
2015-03-10 21:31:18 -04:00
[**--cpuset-cpus**[=*CPUSET-CPUS*]]
2015-04-14 21:33:46 -04:00
[**--cpuset-mems**[=*CPUSET-MEMS*]]
2015-04-20 11:16:47 -04:00
[**--cpu-quota**[=*0*]]
2014-08-19 21:10:42 -04:00
[**--device**[=*[]*]]
[**--dns-search**[=*[]*]]
[**--dns**[=*[]*]]
[**-e**|**--env**[=*[]*]]
[**--entrypoint**[=*ENTRYPOINT*]]
[**--env-file**[=*[]*]]
[**--expose**[=*[]*]]
[**-h**|**--hostname**[=*HOSTNAME*]]
2014-10-15 17:14:12 -04:00
[**--help**]
2014-08-19 21:10:42 -04:00
[**-i**|**--interactive**[=*false*]]
2014-11-27 23:21:55 -05:00
[**--ipc**[=*IPC*]]
2015-02-16 19:36:03 -05:00
[**-l**|**--label**[=*[]*]]
[**--label-file**[=*[]*]]
2014-08-19 21:10:42 -04:00
[**--link**[=*[]*]]
[**--lxc-conf**[=*[]*]]
2015-02-05 19:24:47 -05:00
[**--log-driver**[=*[]*]]
2015-05-21 16:20:25 -04:00
[**--log-opt**[=*[]*]]
2014-08-19 21:10:42 -04:00
[**-m**|**--memory**[=*MEMORY*]]
2015-02-04 20:12:56 -05:00
[**--memory-swap**[=*MEMORY-SWAP*]]
2014-11-27 23:21:55 -05:00
[**--mac-address**[=*MAC-ADDRESS*]]
2014-08-19 21:10:42 -04:00
[**--name**[=*NAME*]]
[**--net**[=*"bridge"*]]
2015-02-26 06:53:55 -05:00
[**--oom-kill-disable**[=*false*]]
2014-08-19 21:10:42 -04:00
[**-P**|**--publish-all**[=*false*]]
[**-p**|**--publish**[=*[]*]]
2014-11-25 15:10:53 -05:00
[**--pid**[=*[]*]]
2015-05-05 18:32:36 -04:00
[**--uts**[=*[]*]]
2014-08-19 21:10:42 -04:00
[**--privileged**[=*false*]]
2015-01-13 16:52:51 -05:00
[**--read-only**[=*false*]]
2014-09-25 02:07:55 -04:00
[**--restart**[=*RESTART*]]
2014-11-27 23:21:55 -05:00
[**--security-opt**[=*[]*]]
2014-08-19 21:10:42 -04:00
[**-t**|**--tty**[=*false*]]
[**-u**|**--user**[=*USER*]]
[**-v**|**--volume**[=*[]*]]
[**--volumes-from**[=*[]*]]
[**-w**|**--workdir**[=*WORKDIR*]]
2015-03-16 19:06:47 -04:00
[**--cgroup-parent**[=*CGROUP-PATH*]]
2014-11-27 23:21:55 -05:00
IMAGE [COMMAND] [ARG...]
2014-08-19 21:10:42 -04:00
2015-05-20 17:51:58 -04:00
# 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'.
2014-08-19 21:10:42 -04:00
# OPTIONS
**-a**, ** --attach**=[]
Attach to STDIN, STDOUT or STDERR.
2014-09-25 02:07:55 -04:00
**--add-host**=[]
Add a custom host-to-IP mapping (host:ip)
2015-05-06 23:55:58 -04:00
**--blkio-weight**=0
Block IO weight (relative weight) accepts a weight value between 10 and 1000.
2014-08-19 21:10:42 -04:00
**-c**, ** --cpu-shares**=0
CPU shares (relative weight)
**--cap-add**=[]
Add Linux capabilities
**--cap-drop**=[]
Drop Linux capabilities
**--cidfile**=""
Write the container ID to the file
2015-03-16 19:06:47 -04:00
**--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.
2015-06-13 12:21:50 -04:00
**--cpu-period**=0
2015-04-08 04:58:59 -04:00
Limit the CPU CFS (Completely Fair Scheduler) period
move resources from Config to HostConfig
Cgroup resources are host dependent, they should be in hostConfig.
For backward compatibility, we just copy it to hostConfig, and leave it in
Config for now, so there is no regressions, but the right way to use this
throught json is to put it in HostConfig, like:
{
"Hostname": "",
...
"HostConfig": {
"CpuShares": 512,
"Memory": 314572800,
...
}
}
As we will add CpusetMems, CpusetCpus is definitely a better name, but some
users are already using Cpuset in their http APIs, we also make it compatible.
The main idea is keep using Cpuset in Config Struct, and make it has the same
value as CpusetCpus, but not always, some scenarios:
- Users use --cpuset in docker command, it can setup cpuset.cpus and can
get Cpuset field from docker inspect or other http API which will get
config info.
- Users use --cpuset-cpus in docker command, ditto.
- Users use Cpuset field in their http APIs, ditto.
- Users use CpusetCpus field in their http APIs, they won't get Cpuset field
in Config info, because by then, they should already know what happens
to Cpuset.
Signed-off-by: Qiang Huang <h.huangqiang@huawei.com>
2015-03-10 21:31:18 -04:00
**--cpuset-cpus**=""
2014-08-19 21:10:42 -04:00
CPUs in which to allow execution (0-3, 0,1)
2015-04-14 21:33:46 -04:00
**--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.
2015-04-20 11:16:47 -04:00
**-cpu-quota**=0
Limit the CPU CFS (Completely Fair Scheduler) quota
2014-08-19 21:10:42 -04:00
**--device**=[]
2014-10-07 23:10:31 -04:00
Add a host device to the container (e.g. --device=/dev/sdc:/dev/xvdc:rwm)
2014-08-19 21:10:42 -04:00
**--dns-search**=[]
2014-10-29 05:17:02 -04:00
Set custom DNS search domains (Use --dns-search=. if you don't wish to set the search domain)
2014-08-19 21:10:42 -04:00
**--dns**=[]
Set custom DNS servers
**-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**=[]
2014-09-16 21:08:30 -04:00
Expose a port or a range of ports (e.g. --expose=3300-3310) from the container without publishing it to your host
2014-08-19 21:10:42 -04:00
**-h**, ** --hostname**=""
Container host name
2014-10-15 17:14:12 -04:00
**--help**
Print usage statement
2014-08-19 21:10:42 -04:00
**-i**, ** --interactive**=*true*|*false*
Keep STDIN open even if not attached. The default is *false* .
2014-11-27 23:21:55 -05:00
**--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.
2015-02-16 19:36:03 -05:00
**-l**, ** --label**=[]
2015-03-17 00:49:33 -04:00
Adds metadata to a container (e.g., --label=com.example.key=value)
2015-02-16 19:36:03 -05:00
**--label-file**=[]
2015-03-17 00:49:33 -04:00
Read labels from a file. Delimit each label with an EOL.
2015-02-16 19:36:03 -05:00
2014-08-19 21:10:42 -04:00
**--link**=[]
2015-05-07 16:02:14 -04:00
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.
2014-08-19 21:10:42 -04:00
**--lxc-conf**=[]
(lxc exec-driver only) Add custom lxc options --lxc-conf="lxc.cgroup.cpuset.cpus = 0,1"
2015-05-29 17:00:46 -04:00
**--log-driver**="|*json-file*|*syslog*|*journald*|*gelf*|*none*"
2015-02-05 19:24:47 -05:00
Logging driver for container. Default is defined by daemon `--log-driver` flag.
**Warning** : `docker logs` command works only for `json-file` logging driver.
2015-05-21 16:20:25 -04:00
**--log-opt**=[]
Logging driver specific options.
2014-08-19 21:10:42 -04:00
**-m**, ** --memory**=""
Memory limit (format: < number > < optional unit > , where unit = b, k, m or g)
2015-02-04 20:12:56 -05:00
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).
**--memory-swap**=""
Total memory limit (memory + swap)
Set `-1` to disable swap (format: < number >< optional unit > , where unit = b, k, m or g).
2015-05-25 13:39:56 -04:00
This value should always larger than ** -m**, so you should always use this with ** -m**.
2015-02-04 20:12:56 -05:00
2014-11-27 23:21:55 -05:00
**--mac-address**=""
Container MAC address (e.g. 92:d0:c6:0a:29:33)
2014-08-19 21:10:42 -04:00
**--name**=""
Assign a name to the container
**--net**="bridge"
Set the Network mode for the container
'bridge': creates a new network stack for the container on the docker bridge
'none': no networking for this container
'container:< name | id > ': reuses another container network stack
'host': use the host network stack inside the container. Note: the host mode gives the container full access to local system services such as D-bus and is therefore considered insecure.
2015-02-26 06:53:55 -05:00
**--oom-kill-disable**=*true*|*false*
Whether to disable OOM Killer for the container or not.
2014-08-19 21:10:42 -04:00
**-P**, ** --publish-all**=*true*|*false*
2015-01-06 02:01:10 -05:00
Publish all exposed ports to random ports on the host interfaces. The default is *false* .
2014-08-19 21:10:42 -04:00
**-p**, ** --publish**=[]
2014-11-03 13:15:55 -05:00
Publish a container's port, or a range of ports, to the host
2014-09-25 02:07:55 -04:00
format: ip:hostPort:containerPort | ip::containerPort | hostPort:containerPort | containerPort
2014-11-03 13:15:55 -05:00
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` )
2014-08-19 21:10:42 -04:00
(use 'docker port' to see the actual mapping)
2014-11-25 15:10:53 -05:00
**--pid**=host
Set the PID mode for the container
**host** : 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.
2015-05-05 18:32:36 -04:00
**--uts**=host
Set the UTS mode for the container
**host** : 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.
2014-08-19 21:10:42 -04:00
**--privileged**=*true*|*false*
Give extended privileges to this container. The default is *false* .
2015-01-13 16:52:51 -05:00
**--read-only**=*true*|*false*
2015-02-04 20:12:56 -05:00
Mount the container's root filesystem as read only.
2015-01-13 16:52:51 -05:00
2015-03-09 22:09:12 -04:00
**--restart**="no"
2014-09-25 02:07:55 -04:00
Restart policy to apply when a container exits (no, on-failure[:max-retry], always)
2014-11-27 23:21:55 -05:00
**--security-opt**=[]
Security Options
2014-08-19 21:10:42 -04:00
**-t**, ** --tty**=*true*|*false*
Allocate a pseudo-TTY. The default is *false* .
**-u**, ** --user**=""
Username or UID
**-v**, ** --volume**=[]
Bind mount a volume (e.g., from the host: -v /host:/container, from Docker: -v /container)
**--volumes-from**=[]
Mount volumes from the specified container(s)
**-w**, ** --workdir**=""
Working directory inside the container
# HISTORY
August 2014, updated by Sven Dowideit < SvenDowideit @ home . org . au >
2014-09-25 02:07:55 -04:00
September 2014, updated by Sven Dowideit < SvenDowideit @ home . org . au >
2014-11-27 23:21:55 -05:00
November 2014, updated by Sven Dowideit < SvenDowideit @ home . org . au >