fix(backend): recover from container name collisions on cluster start#93
Merged
Conversation
Ximaz
approved these changes
May 17, 2026
a9ex
force-pushed
the
fix/cluster-name-collision
branch
from
6ef3c51 to
66b98fe
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Description
Briefly describe what this PR does :
Backend now recovers from a name collision when creating a cluster's container. Previously, a stale container left behind by an external docker stop (without docker rm) or a previous incomplete teardown would block every subsequent
start()with a 409 Conflict, and the user had to clean up manually with the Docker CLI.Context / Motivation
Explain why this change is needed:
Related Links
Screenshots (if applicable)
Checklist
Additional Notes