Skip to content

Fix the inability to restart the Compose stack after network configuration change - #12898

Closed
andrii-telesh-readdle wants to merge 1 commit into
docker:mainfrom
andrii-telesh-readdle:fix/issue-12897-drop-containers-for-diverged-network
Closed

Fix the inability to restart the Compose stack after network configuration change#12898
andrii-telesh-readdle wants to merge 1 commit into
docker:mainfrom
andrii-telesh-readdle:fix/issue-12897-drop-containers-for-diverged-network

Conversation

@andrii-telesh-readdle

Copy link
Copy Markdown
Contributor

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

Comment threadpkg/compose/create.go Outdated
@andrii-telesh-readdle
andrii-telesh-readdleforce-pushed the fix/issue-12897-drop-containers-for-diverged-network branch from 4f9c86a to c9d5d48CompareJune 2, 2025 15:59
@ndeloof

Copy link
Copy Markdown
Contributor

see #12899 as an alternative fix

@ndeloofndeloof closed this Jun 2, 2025
@andrii-telesh-readdle
andrii-telesh-readdle deleted the fix/issue-12897-drop-containers-for-diverged-network branch June 2, 2025 17:39
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[BUG] docker-compose up fails after removing a diverged network

2 participants

@andrii-telesh-readdle@ndeloof