Repository navigation
Remote cache improvements #6847
MatthiasGrandl
started this conversation in
Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
I have been evaluating switching our CI from buildkit to buildah for various reasons. The only thing that prevents me currently is that cached builds are minutes faster on buildkit.
I do like how simple --cache-to --cache-from is compared to buildkit, but I feel like there is a lot of time/bandwidth left on the table.
Skimming stage_executor.go, the current flow is per-step pull → run → push. For builds where most steps cache-hit against a registry, that's a lot of sequential round-trips, and buildkit avoids most of them by probing the registry without materializing blobs and deferring uploads.
I was thinking:
Plus a smaller standalone win: if every step cache-hits and the final manifest already exists at the destination, skip the copy and just retag.
Is there a structural reason the per-step pull/push is the way it is today that I'm missing? Does my plan sound too naive?
Addresses #6365
All reactions