start new API v1.17 docs
Signed-off-by: Jean-Tiare Le Bigot <jt@yadutaf.fr> Upstream-commit: 800a8e896e810019b625ad0161c4fc4a04c26845 Component: engine
This commit is contained in:
@ -30,13 +30,26 @@ page_keywords: API, Docker, rcli, REST, documentation
|
||||
Client applications need to take this into account to ensure
|
||||
they will not break when talking to newer Docker daemons.
|
||||
|
||||
The current version of the API is v1.16
|
||||
The current version of the API is v1.17
|
||||
|
||||
Calling `/info` is the same as calling
|
||||
`/v1.16/info`.
|
||||
`/v1.17/info`.
|
||||
|
||||
You can still call an old version of the API using
|
||||
`/v1.15/info`.
|
||||
`/v1.16/info`.
|
||||
|
||||
## v1.17
|
||||
|
||||
### Full Documentation
|
||||
|
||||
[*Docker Remote API v1.17*](/reference/api/docker_remote_api_v1.17/)
|
||||
|
||||
### What's new
|
||||
|
||||
`POST /containers/(id)/attach` and `POST /exec/(id)/start`
|
||||
|
||||
**New!**
|
||||
Docker client now hints potential proxies about connection hijacking using HTTP Upgrade headers.
|
||||
|
||||
## v1.16
|
||||
|
||||
|
||||
Reference in New Issue
Block a user