fix: launching from local images in kubernetes #1830
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.
When launching using Kubernetes provider (
zombienet -p kubernetes
) and using minikube, I needed to use local image without publishing it.I can add it to
minikube
, by usingminikube image load image-name:tag
and specify inzombienet.toml
:However, it'd still fail at the creating bootnodes (and running --help commands), because the policy was to Always download images and they were not published.
Ideally, this option probably should be sourced from
networkSpec.settings.image_pull_policy
, but I left it at this level.Let me know what you think!
Sort of related to #1829 (as a workaround to not having private registries)