github.com/vincentwoo/docker@v0.7.3-0.20160116130405-82401a4b13c0/docs/reference/api/docker_remote_api.md (about) 1 <!--[metadata]> 2 +++ 3 title = "Remote API" 4 description = "API Documentation for Docker" 5 keywords = ["API, Docker, rcli, REST, documentation"] 6 [menu.main] 7 parent = "smn_remoteapi" 8 weight=-3 9 +++ 10 <![end-metadata]--> 11 12 # Docker Remote API 13 14 Docker's Remote API uses an open schema model. In this model, unknown 15 properties in incoming messages are ignored. Client applications need to take 16 this behavior into account to ensure they do not break when talking to newer 17 Docker daemons. 18 19 The API tends to be REST, but for some complex commands, like attach or pull, 20 the HTTP connection is hijacked to transport STDOUT, STDIN, and STDERR. 21 22 By default the Docker daemon listens on `unix:///var/run/docker.sock` and the 23 client must have `root` access to interact with the daemon. If a group named 24 `docker` exists on your system, `docker` applies ownership of the socket to the 25 group. 26 27 The current version of the API is v1.23 which means calling `/info` is the same 28 as calling `/v1.23/info`. To call an older version of the API use 29 `/v1.22/info`. 30 31 Use the table below to find the API version for a Docker version: 32 33 Docker version | API version | Changes 34 ----------------|------------------------------------|------------------------------------------------------ 35 1.11.x | [1.23](docker_remote_api_v1.23.md) | [API changes](docker_remote_api.md#v1-23-api-changes) 36 1.10.x | [1.22](docker_remote_api_v1.22.md) | [API changes](docker_remote_api.md#v1-22-api-changes) 37 1.9.x | [1.21](docker_remote_api_v1.21.md) | [API changes](docker_remote_api.md#v1-21-api-changes) 38 1.8.x | [1.20](docker_remote_api_v1.20.md) | [API changes](docker_remote_api.md#v1-20-api-changes) 39 1.7.x | [1.19](docker_remote_api_v1.19.md) | [API changes](docker_remote_api.md#v1-19-api-changes) 40 1.6.x | [1.18](docker_remote_api_v1.18.md) | [API changes](docker_remote_api.md#v1-18-api-changes) 41 1.5.x | [1.17](docker_remote_api_v1.17.md) | [API changes](docker_remote_api.md#v1-17-api-changes) 42 1.4.x | [1.16](docker_remote_api_v1.16.md) | [API changes](docker_remote_api.md#v1-16-api-changes) 43 1.3.x | [1.15](docker_remote_api_v1.15.md) | [API changes](docker_remote_api.md#v1-15-api-changes) 44 1.2.x | [1.14](docker_remote_api_v1.14.md) | [API changes](docker_remote_api.md#v1-14-api-changes) 45 46 Refer to the [GitHub repository]( 47 https://github.com/docker/docker/tree/master/docs/reference/api) for 48 older releases. 49 50 ## Authentication 51 52 Since API version 1.2, the auth configuration is now handled client side, so the 53 client has to send the `authConfig` as a `POST` in `/images/(name)/push`. The 54 `authConfig`, set as the `X-Registry-Auth` header, is currently a Base64 encoded 55 (JSON) string with the following structure: 56 57 ``` 58 {"username": "string", "password": "string", "email": "string", 59 "serveraddress" : "string", "auth": ""} 60 ``` 61 62 Callers should leave the `auth` empty. The `serveraddress` is a domain/ip 63 without protocol. Throughout this structure, double quotes are required. 64 65 ## Using Docker Machine with the API 66 67 If you are using `docker-machine`, the Docker daemon is on a virtual host that uses an encrypted TCP socket. This means, for Docker Machine users, you need to add extra parameters to `curl` or `wget` when making test API requests, for example: 68 69 ``` 70 curl --insecure --cert ~/.docker/cert.pem --key ~/.docker/key.pem https://YOUR_VM_IP:2376/images/json 71 72 wget --no-check-certificate --certificate=$DOCKER_CERT_PATH/cert.pem --private-key=$DOCKER_CERT_PATH/key.pem https://your_vm_ip:2376/images/json -O - -q 73 ``` 74 75 ## Docker Events 76 77 The following diagram depicts the container states accessible through the API. 78 79  80 81 Some container-related events are not affected by container state, so they are not included in this diagram. These events are: 82 83 * **export** emitted by `docker export` 84 * **exec_create** emitted by `docker exec` 85 * **exec_start** emitted by `docker exec` after **exec_create** 86 87 Running `docker rmi` emits an **untag** event when removing an image name. The `rmi` command may also emit **delete** events when images are deleted by ID directly or by deleting the last tag referring to the image. 88 89 > **Acknowledgement**: This diagram and the accompanying text were used with the permission of Matt Good and Gilder Labs. See Matt's original blog post [Docker Events Explained](http://gliderlabs.com/blog/2015/04/14/docker-events-explained/). 90 91 ## Version history 92 93 This section lists each version from latest to oldest. Each listing includes a link to the full documentation set and the changes relevant in that release. 94 95 ### v1.23 API changes 96 97 [Docker Remote API v1.23](docker_remote_api_v1.23.md) documentation 98 99 100 ### v1.22 API changes 101 102 [Docker Remote API v1.22](docker_remote_api_v1.22.md) documentation 103 104 * `POST /container/(name)/update` updates the resources of a container. 105 * `GET /containers/json` supports filter `isolation` on Windows. 106 * `GET /containers/json` now returns the list of networks of containers. 107 * `GET /info` Now returns `Architecture` and `OSType` fields, providing information 108 about the host architecture and operating system type that the daemon runs on. 109 * `GET /networks/(name)` now returns a `Name` field for each container attached to the network. 110 * `GET /version` now returns the `BuildTime` field in RFC3339Nano format to make it 111 consistent with other date/time values returned by the API. 112 * `AuthConfig` now supports a `registrytoken` for token based authentication 113 * `POST /containers/create` now has a 4M minimum value limit for `HostConfig.KernelMemory` 114 * Pushes initiated with `POST /images/(name)/push` and pulls initiated with `POST /images/create` 115 will be cancelled if the HTTP connection making the API request is closed before 116 the push or pull completes. 117 * `POST /containers/create` now allows you to set a read/write rate limit for a 118 device (in bytes per second or IO per second). 119 * `GET /networks` now supports filtering by `name`, `id` and `type`. 120 * `POST /containers/create` now allows you to set the static IPv4 and/or IPv6 address for the container. 121 * `POST /networks/(id)/connect` now allows you to set the static IPv4 and/or IPv6 address for the container. 122 * `GET /info` now includes the number of containers running, stopped, and paused. 123 * `POST /networks/create` now supports restricting external access to the network by setting the `internal` field. 124 * `POST /networks/(id)/disconnect` now includes a `Force` option to forcefully disconnect a container from network 125 * `GET /containers/(id)/json` now returns the `NetworkID` of containers. 126 * `POST /networks/create` Now supports an options field in the IPAM config that provides options 127 for custom IPAM plugins. 128 * `GET /networks/{network-id}` Now returns IPAM config options for custom IPAM plugins if any 129 are available. 130 * `GET /networks/<network-id>` now returns subnets info for user-defined networks. 131 132 ### v1.21 API changes 133 134 [Docker Remote API v1.21](docker_remote_api_v1.21.md) documentation 135 136 * `GET /volumes` lists volumes from all volume drivers. 137 * `POST /volumes/create` to create a volume. 138 * `GET /volumes/(name)` get low-level information about a volume. 139 * `DELETE /volumes/(name)` remove a volume with the specified name. 140 * `VolumeDriver` was moved from `config` to `HostConfig` to make the configuration portable. 141 * `GET /images/(name)/json` now returns information about an image's `RepoTags` and `RepoDigests`. 142 * The `config` option now accepts the field `StopSignal`, which specifies the signal to use to kill a container. 143 * `GET /containers/(id)/stats` will return networking information respectively for each interface. 144 * The `HostConfig` option now includes the `DnsOptions` field to configure the container's DNS options. 145 * `POST /build` now optionally takes a serialized map of build-time variables. 146 * `GET /events` now includes a `timenano` field, in addition to the existing `time` field. 147 * `GET /events` now supports filtering by image and container labels. 148 * `GET /info` now lists engine version information and return the information of `CPUShares` and `Cpuset`. 149 * `GET /containers/json` will return `ImageID` of the image used by container. 150 * `POST /exec/(name)/start` will now return an HTTP 409 when the container is either stopped or paused. 151 * `GET /containers/(name)/json` now accepts a `size` parameter. Setting this parameter to '1' returns container size information in the `SizeRw` and `SizeRootFs` fields. 152 * `GET /containers/(name)/json` now returns a `NetworkSettings.Networks` field, 153 detailing network settings per network. This field deprecates the 154 `NetworkSettings.Gateway`, `NetworkSettings.IPAddress`, 155 `NetworkSettings.IPPrefixLen`, and `NetworkSettings.MacAddress` fields, which 156 are still returned for backward-compatibility, but will be removed in a future version. 157 * `GET /exec/(id)/json` now returns a `NetworkSettings.Networks` field, 158 detailing networksettings per network. This field deprecates the 159 `NetworkSettings.Gateway`, `NetworkSettings.IPAddress`, 160 `NetworkSettings.IPPrefixLen`, and `NetworkSettings.MacAddress` fields, which 161 are still returned for backward-compatibility, but will be removed in a future version. 162 * The `HostConfig` option now includes the `OomScoreAdj` field for adjusting the 163 badness heuristic. This heuristic selects which processes the OOM killer kills 164 under out-of-memory conditions. 165 166 ### v1.20 API changes 167 168 [Docker Remote API v1.20](docker_remote_api_v1.20.md) documentation 169 170 * `GET /containers/(id)/archive` get an archive of filesystem content from a container. 171 * `PUT /containers/(id)/archive` upload an archive of content to be extracted to 172 an existing directory inside a container's filesystem. 173 * `POST /containers/(id)/copy` is deprecated in favor of the above `archive` 174 endpoint which can be used to download files and directories from a container. 175 * The `hostConfig` option now accepts the field `GroupAdd`, which specifies a 176 list of additional groups that the container process will run as. 177 178 ### v1.19 API changes 179 180 [Docker Remote API v1.19](docker_remote_api_v1.19.md) documentation 181 182 * When the daemon detects a version mismatch with the client, usually when 183 the client is newer than the daemon, an HTTP 400 is now returned instead 184 of a 404. 185 * `GET /containers/(id)/stats` now accepts `stream` bool to get only one set of stats and disconnect. 186 * `GET /containers/(id)/logs` now accepts a `since` timestamp parameter. 187 * `GET /info` The fields `Debug`, `IPv4Forwarding`, `MemoryLimit`, and 188 `SwapLimit` are now returned as boolean instead of as an int. In addition, the 189 end point now returns the new boolean fields `CpuCfsPeriod`, `CpuCfsQuota`, and 190 `OomKillDisable`. 191 * The `hostConfig` option now accepts the fields `CpuPeriod` and `CpuQuota` 192 * `POST /build` accepts `cpuperiod` and `cpuquota` options 193 194 ### v1.18 API changes 195 196 [Docker Remote API v1.18](docker_remote_api_v1.18.md) documentation 197 198 * `GET /version` now returns `Os`, `Arch` and `KernelVersion`. 199 * `POST /containers/create` and `POST /containers/(id)/start`allow you to set ulimit settings for use in the container. 200 * `GET /info` now returns `SystemTime`, `HttpProxy`,`HttpsProxy` and `NoProxy`. 201 * `GET /images/json` added a `RepoDigests` field to include image digest information. 202 * `POST /build` can now set resource constraints for all containers created for the build. 203 * `CgroupParent` can be passed in the host config to setup container cgroups under a specific cgroup. 204 * `POST /build` closing the HTTP request cancels the build 205 * `POST /containers/(id)/exec` includes `Warnings` field to response. 206 207 ### v1.17 API changes 208 209 [Docker Remote API v1.17](docker_remote_api_v1.17.md) documentation 210 211 * The build supports `LABEL` command. Use this to add metadata to an image. For 212 example you could add data describing the content of an image. `LABEL 213 "com.example.vendor"="ACME Incorporated"` 214 * `POST /containers/(id)/attach` and `POST /exec/(id)/start` 215 * The Docker client now hints potential proxies about connection hijacking using HTTP Upgrade headers. 216 * `POST /containers/create` sets labels on container create describing the container. 217 * `GET /containers/json` returns the labels associated with the containers (`Labels`). 218 * `GET /containers/(id)/json` returns the list current execs associated with the 219 container (`ExecIDs`). This endpoint now returns the container labels 220 (`Config.Labels`). 221 * `POST /containers/(id)/rename` renames a container `id` to a new name.* 222 * `POST /containers/create` and `POST /containers/(id)/start` callers can pass 223 `ReadonlyRootfs` in the host config to mount the container's root filesystem as 224 read only. 225 * `GET /containers/(id)/stats` returns a live stream of a container's resource usage statistics. 226 * `GET /images/json` returns the labels associated with each image (`Labels`). 227 228 229 ### v1.16 API changes 230 231 [Docker Remote API v1.16](docker_remote_api_v1.16.md) 232 233 * `GET /info` returns the number of CPUs available on the machine (`NCPU`), 234 total memory available (`MemTotal`), a user-friendly name describing the running Docker daemon (`Name`), a unique ID identifying the daemon (`ID`), and 235 a list of daemon labels (`Labels`). 236 * `POST /containers/create` callers can set the new container's MAC address explicitly. 237 * Volumes are now initialized when the container is created. 238 * `POST /containers/(id)/copy` copies data which is contained in a volume. 239 240 ### v1.15 API changes 241 242 [Docker Remote API v1.15](docker_remote_api_v1.15.md) documentation 243 244 `POST /containers/create` you can set a container's `HostConfig` when creating a 245 container. Previously this was only available when starting a container. 246 247 ### v1.14 API changes 248 249 [Docker Remote API v1.14](docker_remote_api_v1.14.md) documentation 250 251 * `DELETE /containers/(id)` when using `force`, the container will be immediately killed with SIGKILL. 252 * `POST /containers/(id)/start` the `HostConfig` option accepts the field `CapAdd`, which specifies a list of capabilities 253 to add, and the field `CapDrop`, which specifies a list of capabilities to drop. 254 * `POST /images/create` th `fromImage` and `repo` parameters support the 255 `repo:tag` format. Consequently, the `tag` parameter is now obsolete. Using the 256 new format and the `tag` parameter at the same time will return an error.