a3639e6ac6
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>
(cherry picked from commit
|
||
---|---|---|
.. | ||
apparmor | ||
builder | ||
completion | ||
desktop-integration | ||
docker-device-tool | ||
docker-engine-selinux | ||
gitdm | ||
httpserver | ||
init | ||
mkimage | ||
nnp-test | ||
reprepro | ||
syntax | ||
syscall-test | ||
udev | ||
vagrant-docker | ||
check-config.sh | ||
dockerize-disk.sh | ||
download-frozen-image-v1.sh | ||
download-frozen-image-v2.sh | ||
mkimage-alpine.sh | ||
mkimage-arch-pacman.conf | ||
mkimage-arch.sh | ||
mkimage-archarm-pacman.conf | ||
mkimage-busybox.sh | ||
mkimage-crux.sh | ||
mkimage-debootstrap.sh | ||
mkimage-rinse.sh | ||
mkimage-yum.sh | ||
mkimage.sh | ||
nuke-graph-directory.sh | ||
project-stats.sh | ||
README.md | ||
report-issue.sh | ||
REVIEWERS |
The contrib
directory contains scripts, images, and other helpful things
which are not part of the core docker distribution. Please note that they
could be out of date, since they do not receive the same attention as the
rest of the repository.