interlock: Default update failure action is now rollback

This behaviour changed in Interlock 2.3.0, which was backported to all
active UCP versions.

The change was tracked by ENGCORE-117.

Signed-off-by: Euan Harris <euan.harris@docker.com>
This commit is contained in:
Euan Harris 2019-11-11 09:29:09 -08:00
parent 15e8fbdcda
commit 3129228e22
1 changed files with 5 additions and 5 deletions

View File

@ -38,15 +38,15 @@ service and save it to a file:
ucp-interlock
```
By default, the `ucp-interlock` service is configured to pause if you provide an
invalid configuration. The service will not restart without manual intervention.
By default, the `ucp-interlock` service is configured to roll back to
a previous stable configuration if you provide an invalid configuration.
If you want the service to automatically rollback to a previous stable
configuration, you can update it with the following command:
If you want the service to pause instead of rolling back, you can update
it with the following command:
```bash
docker service update \
--update-failure-action rollback \
--update-failure-action pause \
ucp-interlock
```