Move Isolation API changes to the correct version
Commit d91c5f42eb
added
support for "Isolation" mode for services, but didn't
get merged before API 1.34.
This patch moves the description in the API version
history to the correct API version (1.35), and does
a slight rewording of the functionality.
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
This commit is contained in:
parent
d91c5f42eb
commit
4533a16fa9
1 changed files with 7 additions and 1 deletions
|
@ -15,6 +15,13 @@ keywords: "API, Docker, rcli, REST, documentation"
|
|||
|
||||
## v1.35 API changes
|
||||
|
||||
[Docker Engine API v1.35](https://docs.docker.com/engine/api/v1.35/) documentation
|
||||
|
||||
* `POST /services/create` and `POST /services/(id)/update` now accepts an
|
||||
`Isolation` field on container spec to set the Isolation technology of the
|
||||
containers running the service (`default`, `process`, or `hyperv`). This
|
||||
configuration is only used for Windows containers.
|
||||
|
||||
|
||||
## v1.34 API changes
|
||||
|
||||
|
@ -26,7 +33,6 @@ keywords: "API, Docker, rcli, REST, documentation"
|
|||
If `Error` is `null`, container removal has succeeded, otherwise
|
||||
the test of an error message indicating why container removal has failed
|
||||
is available from `Error.Message` field.
|
||||
* `POST /services/create` and `POST /services/(id)/update` now accept an `Isolation` field on container spec
|
||||
|
||||
## v1.33 API changes
|
||||
|
||||
|
|
Loading…
Add table
Reference in a new issue