Use BuildKit registry caching to speed up builds #114
Merged
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
docker buildtodocker buildx buildwith registry-based layer cachingnpm cideps stage) across builds, saving ~1 min when dependencies haven't changedbuildx --pushhandles it) and the redundantimagesblock_IMAGEsubstitution to reduce repetitionHow it works
Each build pushes cached layers to
...:cache-prod/...:cache-stagingtags. Subsequent builds pull those layers before building, so unchanged layers (likenpm ci) are reused.First build after this merges will be the same speed (no cache yet). Subsequent builds should save ~1 min.
Test plan
🤖 Generated with Claude Code