Skip to content

Replace old with new in container-draining.md #53

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

Merged
wowu merged 1 commit into from
Jul 7, 2025
Merged

Replace old with new in container-draining.md #53

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
2 changes: 1 addition & 1 deletion docs/container-draining.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -60,7 +60,7 @@ If you want to make sure that no requests are lost during deployment, you can us
With this configuration, a rollout process looks like this:

1. New container is started.
2. Docker daemon marks the old container as healthy.
2. Docker daemon marks the new container as healthy.
3. Proxy starts sending requests to the new container alongside the old container.
4. We create `/tmp/drain` file in the old container.
5. Docker daemon marks the old container as unhealthy.
Expand Down