fix(runner): isolate Buildx builders - #125
Merged
Merged
Conversation
Scope builder names to each job so concurrent cleanup cannot stop sibling builds. Co-authored-by: Codex <codex@openai.com> Signed-off-by: Alexey Zhokhov <alexey@zhokhov.com>
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
1 participant
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 jobs previously reused the global
velnor-buildername. A finishing job could remove that shared BuildKit container while siblings were exporting images, producinggraceful_stop/ EOF failures.Scope the effective builder name to the job workspace identity. Setup, outputs, build invocations, and post cleanup now consistently use the job-owned builder.
Verify locally
Signed-off-by: Alexey Zhokhov alexey@zhokhov.com
Co-authored-by: Codex codex@openai.com