Add support for max layer caching in build #477
Draft
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.
With the change to buildkit as the default option, layers which are not required for the final image are not cached.
This PR support caching of all images in a build process, specifically by leveraging the containerd image store and the flag
mode=max
for the cache-to.It requires:
CACHE_TO
flagCACHE_FROM_EXPLICIT
flag which can take an image name of the formtype=registry,ref=<registry>/<cache-image>:<branch>
Build using the standard instructions.
Testing:
go mod init
mode=min
andmode=max
and you can see the different sizes of content pushed to the repository