-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
How to build a node image with preloaded docker images #2063
Comments
This is not supported currently. It's possible to reproduce what kind does internally, but you'd have to do it yourself, and it's going to be clunky and brittle (you can't do this in a normal I recommend just using a local registry, or saving all the images you want to a tarball (e.g. |
I have the same use-case, for air-gapped installations it would be great to be able to build a custom image with additional images pre-loaded. |
see: #2160 for current discussion 😅 |
I noticed this PR as well - #2303. Wonder if this might be something that I could try? I essentially want to prime by kind node with some docker images to speed up my CI pipeline (since pulling images takes a lot of time at the moment leading to slow tests) |
You will still have to pull down the content of course, the total download size is not easily decreased, but it can be done at a different point in the process (arguably one that is less concurrent and not necessarily net improvement in performance, unless you are managing to cache images at the CI level, in which case it may be a big win) |
Is there a way to build a node image with some preloaded docker images/tars, then when the cluster is created with
kind create cluster --image
, those docker images will need not be pulled inside or loaded into kind.The text was updated successfully, but these errors were encountered: