-
Notifications
You must be signed in to change notification settings - Fork 389
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Question: can we extract KOCACHE instead of saving it to disk to be able use it between stateless builds? #809
Comments
kindly ping @jonjohnsonjr |
I think we can store this information in the annotations of the image manifest (which might be verbose) or labels of the image config, as BuildKit did, and read that information over here instead of the disk. AFAIK, ko uses some mapping between the buildIDs to diffIDs and diffIDs to the descriptor, so, we can use the diffID as key and descriptor JSON as a value in the annotations or the labels sections. WDYT? |
Hey sorry, I was on leave for a while 😅 Yes, this is definitely something we could do! I jotted down some notes a while back, let me just dump them here:
I think what you're describing is very similar to what I had in mind here? |
This issue is stale because it has been open for 90 days with no |
AFAIK, KOCACHE only accepts directories as a value. But we couldn't use this cache between stateless builds. For example, each workflow run executes in a fresh VM in GitHub Actions.
It'd be nice if we could use OCI registries to save the cache for ko builds.
The text was updated successfully, but these errors were encountered: