docker
/
docs
mirror of https://github.com/docker/docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
docs/content/engine/api/_index.md

164 lines
8.1 KiB
Markdown
Raw Blame History

---
title: Develop with Docker Engine API
description: Learn how you can use Docker Engine API and SDKs in the language of your choice.
keywords: developing, api, Docker Engine API, API versions, SDK versions
aliases:
- /engine/reference/api/
- /engine/reference/api/docker_remote_api/
- /reference/api/
- /reference/api/docker_remote_api/
- /reference/api/docker_remote_api_v1.0/
- /reference/api/docker_remote_api_v1.1/
- /reference/api/docker_remote_api_v1.2/
- /reference/api/docker_remote_api_v1.3/
- /reference/api/docker_remote_api_v1.4/
- /reference/api/docker_remote_api_v1.5/
- /reference/api/docker_remote_api_v1.6/
- /reference/api/docker_remote_api_v1.7/
- /reference/api/docker_remote_api_v1.8/
- /reference/api/docker_remote_api_v1.9/
- /reference/api/docker_remote_api_v1.10/
- /reference/api/docker_remote_api_v1.11/
- /reference/api/docker_remote_api_v1.12/
- /reference/api/docker_remote_api_v1.13/
- /reference/api/docker_remote_api_v1.14/
- /reference/api/docker_remote_api_v1.15/
- /reference/api/docker_remote_api_v1.16/
- /reference/api/docker_remote_api_v1.17/
---
Docker provides an API for interacting with the Docker daemon (called the Docker
Engine API), as well as SDKs for Go and Python. The SDKs allow you to efficiently build and
scale Docker apps and solutions. If Go or Python don't work
for you, you can use the Docker Engine API directly.
For information about Docker Engine SDKs, see [Develop with Docker Engine SDKs](sdk/index.md).
The Docker Engine API is a RESTful API accessed by an HTTP client such as `wget` or
`curl`, or the HTTP library which is part of most modern programming languages.
## View the API reference
You can
[view the reference for the latest version of the API](latest/index.html)
or [choose a specific version](/engine/api/version-history/).
## Versioned API and SDK
The version of the Docker Engine API you should use depends upon the version of
your Docker daemon and Docker client.
A given version of the Docker Engine SDK supports a specific version of the
Docker Engine API, as well as all earlier versions. If breaking changes occur,
they are documented prominently.
> **Note**
>
> The Docker daemon and client don't necessarily need to be the same version
> at all times. However, keep the following in mind.
>
> - If the daemon is newer than the client, the client doesn't know about new
> features or deprecated API endpoints in the daemon.
>
> - If the client is newer than the daemon, the client can request API
> endpoints that the daemon doesn't know about.
A new version of the API is released when new features are added. The Docker API
is backward-compatible, so you don't need to update code that uses the API
unless you need to take advantage of new features.
To see the highest version of the API your Docker daemon and client support, use
`docker version`:
```console
$ docker version
Client: Docker Engine - Community
Version: 26.0.0
API version: 1.45
Go version: go1.21.8
Git commit: 2ae903e
Built: Wed Mar 20 15:17:48 2024
OS/Arch: linux/amd64
Context: default
Server: Docker Engine - Community
Engine:
Version: 26.0.0
API version: 1.45 (minimum version 1.24)
Go version: go1.21.8
Git commit: 8b79278
Built: Wed Mar 20 15:17:48 2024
OS/Arch: linux/amd64
Experimental: false
...
```
You can specify the API version to use in any of the following ways:
- When using the SDK, use the latest version. At a minimum, use the version
that incorporates the API version with the features you need.
- When using `curl` directly, specify the version as the first part of the URL.
For instance, if the endpoint is `/containers/` you can use
`/v1.45/containers/`.
- To force the Docker CLI or the Docker Engine SDKs to use an older version
of the API than the version reported by `docker version`, set the
environment variable `DOCKER_API_VERSION` to the correct version. This works
on Linux, Windows, or macOS clients.
```console
$ DOCKER_API_VERSION='1.44'
```
While the environment variable is set, that version of the API is used, even
if the Docker daemon supports a newer version. This environment variable
disables API version negotiation, so you should only use it if you must
use a specific version of the API, or for debugging purposes.
- The Docker Go SDK allows you to enable API version negotiation, automatically
selects an API version that's supported by both the client and the Docker Engine
that's in use.
- For the SDKs, you can also specify the API version programmatically as a
parameter to the `client` object. See the
[Go constructor](https://pkg.go.dev/github.com/docker/docker/client#NewClientWithOpts)
or the
[Python SDK documentation for `client`](https://docker-py.readthedocs.io/en/stable/client.html).
### API version matrix
| Docker version | Maximum API version | Change log |
|:---------------|:---------------------------|:---------------------------------------------------------|
| 26.0 | [1.45](/engine/api/v1.45/) | [changes](/engine/api/version-history/#v145-api-changes) |
| 25.0 | [1.44](/engine/api/v1.44/) | [changes](/engine/api/version-history/#v144-api-changes) |
| 24.0 | [1.43](/engine/api/v1.43/) | [changes](/engine/api/version-history/#v143-api-changes) |
| 23.0 | [1.42](/engine/api/v1.42/) | [changes](/engine/api/version-history/#v142-api-changes) |
| 20.10 | [1.41](/engine/api/v1.41/) | [changes](/engine/api/version-history/#v141-api-changes) |
| 19.03 | [1.40](/engine/api/v1.40/) | [changes](/engine/api/version-history/#v140-api-changes) |
| 18.09 | [1.39](/engine/api/v1.39/) | [changes](/engine/api/version-history/#v139-api-changes) |
| 18.06 | [1.38](/engine/api/v1.38/) | [changes](/engine/api/version-history/#v138-api-changes) |
| 18.05 | [1.37](/engine/api/v1.37/) | [changes](/engine/api/version-history/#v137-api-changes) |
| 18.04 | [1.37](/engine/api/v1.37/) | [changes](/engine/api/version-history/#v137-api-changes) |
| 18.03 | [1.37](/engine/api/v1.37/) | [changes](/engine/api/version-history/#v137-api-changes) |
| 18.02 | [1.36](/engine/api/v1.36/) | [changes](/engine/api/version-history/#v136-api-changes) |
| 17.12 | [1.35](/engine/api/v1.35/) | [changes](/engine/api/version-history/#v135-api-changes) |
| 17.11 | [1.34](/engine/api/v1.34/) | [changes](/engine/api/version-history/#v134-api-changes) |
| 17.10 | [1.33](/engine/api/v1.33/) | [changes](/engine/api/version-history/#v133-api-changes) |
| 17.09 | [1.32](/engine/api/v1.32/) | [changes](/engine/api/version-history/#v132-api-changes) |
| 17.07 | [1.31](/engine/api/v1.31/) | [changes](/engine/api/version-history/#v131-api-changes) |
| 17.06 | [1.30](/engine/api/v1.30/) | [changes](/engine/api/version-history/#v130-api-changes) |
| 17.05 | [1.29](/engine/api/v1.29/) | [changes](/engine/api/version-history/#v129-api-changes) |
| 17.04 | [1.28](/engine/api/v1.28/) | [changes](/engine/api/version-history/#v128-api-changes) |
| 17.03.1 | [1.27](/engine/api/v1.27/) | [changes](/engine/api/version-history/#v127-api-changes) |
| 17.03 | [1.26](/engine/api/v1.27/) | [changes](/engine/api/version-history/#v126-api-changes) |
| 1.13.1 | [1.26](/engine/api/v1.26/) | [changes](/engine/api/version-history/#v126-api-changes) |
| 1.13 | [1.25](/engine/api/v1.26/) | [changes](/engine/api/version-history/#v125-api-changes) |
| 1.12 | [1.24](/engine/api/v1.24/) | [changes](/engine/api/version-history/#v124-api-changes) |
### Deprecated API versions
API versions before v1.24 are [deprecated](/engine/deprecated/#deprecate-legacy-api-versions).
You can find archived documentation for deprecated versions of the API in the
code repository on GitHub:
- [Documentation for API versions 1.23 and before](https://github.com/moby/moby/tree/v25.0.0/docs/api).
- [Documentation for API versions 1.17 and before](https://github.com/moby/moby/tree/v1.9.1/docs/reference/api).
Reference in New Issue View Git Blame Copy Permalink