Feat: Add container layer caching #2962
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
Feat: Adds QEMU emulation and Buildx support
freearhey
approved these changes
Dec 20, 2025
PopeyeTheSai10r
approved these changes
Dec 27, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
Why
Currently each release creates builds from scratch on a fresh worker node.
Caching layers can speed up future releases; if some layers are unchanged, they do not need to be rebuilt.
What
Dockerfile uses layers which can be cached between releases. GitHub has a way of utilising this with GitHub Actions cache to cache build layers.
I am not completely familiar with this project, but the limit for caching is 10GB per repository:
Please see Usage limits and eviction policy
As the Image for this repository is only 300MB, it seems sensible to take advantage of caching layers to speed up future builds.
If there is any reason why this should not be used here, please let me know and we can close this :) ( e.g. cache is being used for other entities )