Skip to content

docs(service create): explain start-first vs stop-first #7199

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
locker95 wants to merge 1 commit into
base: master
Choose a base branch
from
Open

docs(service create): explain start-first vs stop-first #7199

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 13 additions & 0 deletions docs/reference/commandline/service_create.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -249,6 +249,19 @@ maximum of 2 tasks at a time, with `10s` between updates. For more information,
refer to the [rolling updates
tutorial](https://docs.docker.com/engine/swarm/swarm-tutorial/rolling-update/).

`--update-order` (and `--rollback-order`) pick whether a new task starts
before or after the old one stops:

- `stop-first` (default) — stop the old task, then start the replacement.
The published VIP has one fewer backend for that slot until the new
task is Running.
- `start-first` — start the new task first and wait until it is Running
before stopping the old one. The VIP keeps a healthy backend (old, then
both, then new). Needs enough spare capacity on the node for the extra
task.

`--rollback-order` is the same idea when a rollback runs.

### <a name="env"></a> Set environment variables (-e, --env)

This sets an environment variable for all tasks in a service. For example:
Expand Down