39b84d5fbe
Currently, there's no way to restart the tasks of a service without making an actual change to the service. This leads to us giving awkward workarounds as in https://github.com/docker/docker.github.io/pull/178/files, where we tell people to scale a service up and down to restore balance, or make unnecessary changes to trigger a restart. This change adds a --force option to "docker service update", which forces the service to be updated even if no changes require that. Since rolling update parameters are respected, the user can use "docker service --force" to do a rolling restart. For example, the following is supported: docker service update --force --update-parallelism 2 \ --update-delay 5s myservice Since the default value of --update-parallelism is 1, the default behavior is to restart the service one task at a time. Signed-off-by: Aaron Lehmann <aaron.lehmann@docker.com> Upstream-commit: c9fdf9abf8d6443598808809b900d96e04adfcb1 Component: engine
published
| published |
|---|
| false |
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