57ae29aa74
This changes the default behavior so that rolling updates will not proceed once an updated task fails to start, or stops running during the update. Users can use docker service inspect --pretty servicename to see the update status, and if it pauses due to a failure, it will explain that the update is paused, and show the task ID that caused it to pause. It also shows the time since the update started. A new --update-on-failure=(pause|continue) flag selects the behavior. Pause means the update stops once a task fails, continue means the old behavior of continuing the update anyway. In the future this will be extended with additional behaviors like automatic rollback, and flags controlling parameters like how many tasks need to fail for the update to stop proceeding. This is a minimal solution for 1.12. Signed-off-by: Aaron Lehmann <aaron.lehmann@docker.com> |
||
|---|---|---|
| .. | ||
| _static | ||
| images | ||
| docker-io_api.md | ||
| docker_io_accounts_api.md | ||
| docker_remote_api.md | ||
| docker_remote_api_v1.18.md | ||
| docker_remote_api_v1.19.md | ||
| docker_remote_api_v1.20.md | ||
| docker_remote_api_v1.21.md | ||
| docker_remote_api_v1.22.md | ||
| docker_remote_api_v1.23.md | ||
| docker_remote_api_v1.24.md | ||
| docker_remote_api_v1.25.md | ||
| hub_registry_spec.md | ||
| index.md | ||
| README.md | ||
| remote_api_client_libraries.md | ||
This directory holds the authoritative specifications of APIs defined and implemented by Docker. Currently this includes:
- The remote API by which a docker node can be queried over HTTP
- The registry API by which a docker node can download and upload images for storage and sharing
- The index search API by which a docker node can search the public index for images to download
- The docker.io OAuth and accounts API which 3rd party services can use to access account information