Fix the inability to restart the Compose stack after network configuration change #12898
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ndeloof
reviewed
Jun 2, 2025
andrii-telesh-readdle
force-pushed
the
fix/issue-12897-drop-containers-for-diverged-network
branch
from
4f9c86a to
c9d5d48
Compare
|
see #12899 as an alternative fix |
andrii-telesh-readdle
deleted the
fix/issue-12897-drop-containers-for-diverged-network
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What I did
Compose will now remove containers that are related to a diverged network.
The details in the bug report.
Related issue
Fixes #12897