-
Notifications
You must be signed in to change notification settings - Fork 18
Caching (question / enhancement) #9
Comments
Thanks for your interest in CBI!
This is plugin-specific. Docker pluginDocker plugin connects to a random Docker daemon that is running on a Kubernetes node, via a bind-mounted The less number of nodes, the higher probability to hit the cache. (and higher load on the each of the nods) I think we should also extend Docker plugin pod template to support setting BuildKit pluginBuildKit plugins connects to a BuildKit service running on the Kubernetes cluster. The less number of BuildKit replicas, the higher probability to hit the cache. BuildKit also plans to implement cache-aware load-balancing mode: moby/buildkit#62 Buildah pluginBuildah plugin creates an one-shot Buildah does not seem to support instruction cache, AFAIK. img plugin (Not implemented yet)img plugin would creates an one-shot The less number of img pods, the higher probability to hit the cache. GCB plugin (Not implemented yet)Needs investigation. ( https://cloud.google.com/container-builder/docs/speeding-up-builds?hl=en#caching_directories_with_google_cloud_storage ) |
Great summary, thanks for the info! |
Thanks @AkihiroSuda for your great work.
I'm studying how to use the buildkit to build image with cache, and find "cache-aware load-balancing mode" would be a great feature. Do we have plan when to release it? |
It is still under discussion and would still take months for implementation |
OK, thanks~ |
This is awesome.
Can you explain how build and image pull caching can work with cbi? How can I configure one or more of the build tools, e.g. docker, to either cache previous builds or previous image pulls?
Related to kubeflow/kubeflow#289 (comment)
The text was updated successfully, but these errors were encountered: