v2 Backport: Build-time buildcaches for images
#255
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
CodeGat
added
priority:medium
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Closes #254
Background
v3has a build-time buildcache for creation of it's images. Why doesv3get all the fun and we get nothing!In this PR, we backport the build-time buildcache functionality for
0.22images as part ofv2. This cuts down image build time from around 3 hours to less than an hour when the buildcache is hit most of the time.Note
To use the buildcache as part of
docker compose build, you will need to have a GitHub user, GitHub PAT withpackages:write, and a OCI URL to a GitHub package as files incontainers/upstream/secrets/oci-[username|password|url].txtrespectively.The PR
containers/upstream/secrets