Repository navigation
Handle Docker name reservation during concurrent backend startup - #87
Merged
Merged
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
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.
Concurrent Docker creation can reserve the shared container name before the container becomes visible to inspect. A competing client then sees the name conflict and an immediate inspect miss, incorrectly failing startup. The real Docker lifecycle regression exposed this intermittently on main after #86.
On a name conflict, wait briefly and retry inspect for the same backend, with a finite bound and no additional create attempts. Other Docker failures and identity mismatches still fail closed. Await backend acquisition in the proxy and regression harness, and make the unit regression deterministically model the name-reserved/inspect-not-yet-visible interval.
Validation: 35 static/security/forwarding unit tests and the real four-process Docker lifecycle test passed locally. The shared backend already running in production is unchanged by this startup correction.