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