fix: isolate build cache per build-uuid to prevent EOF errors#148
Merged
vigneshrajsb merged 3 commits intomainfrom Mar 27, 2026
Merged
fix: isolate build cache per build-uuid to prevent EOF errors#148vigneshrajsb merged 3 commits intomainfrom
vigneshrajsb merged 3 commits intomainfrom
Conversation
…ite corruption Multiple concurrent builds of the same service (e.g., 130 open PRs for next-web) were all reading/writing the same :cache tag in the distribution registry, causing race conditions that corrupted cache manifests and led to buildkit "unexpected EOF" errors during COPY --from steps. Appends deployUuid to the cache ref for non-ECR registries so each environment/PR gets its own isolated cache entry. Before: distribution.../next-web/service-name:cache (shared) After: distribution.../next-web/service-name/deploy-uuid:cache (per-env)
- Add buildUuid to NativeBuildOptions and pass build.uuid from deploy.ts - Replace two-step cache ref patching with single appendCacheRefSegments() that builds the full path (serviceName + buildUuid) in one call - Cache ref: distribution.../repo/service-name/build-uuid:cache Before: all PRs shared one cache ref per service (concurrent write races) After: each environment gets its own isolated cache ref
- Fix stale comment referencing deployUuid instead of buildUuid - Replace duplicate test with buildUuid:undefined fallback test - Add inline comment explaining why cache is scoped per build-uuid
vigneshrajsb
changed the title
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.
Summary
buildUuid(environment identifier, e.g.,dev-0,wandering-credit-924200) to the buildkit cache ref for non-ECR registries (distribution), so each environment/PR gets its own isolated cache entry:cachetag, causing concurrent write races that corrupted cache manifestsunexpected EOFerrors per 2 days across buildsBefore:
distribution.../repo/service-name:cache(shared across all PRs)After:
distribution.../repo/service-name/build-uuid:cache(isolated per environment)Changes
buildUuidtoNativeBuildOptions, passed fromdeploy.build.uuidappendCacheRefSegments(cacheRef, serviceName, buildUuid)buildUuidis undefined, falls back to service-name-only cache ref (backward compatible)Trade-offs
Test plan