-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Allow using a local infra_image #10318
Comments
Hi @varsanojidan, thanks for the suggestion! Indeed, looks like we don't do the same optimization around checking whether the |
Are there any known sharp corners with this? I don't know what I did to my config, but I now can't pull
And, when I add the pull to my startup script, I successfully pull the image:
But, the error remains. Which would suggest to me that the local infra_image is not being used. Do I need to make sure it's not using latest? |
I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues. |
Proposal
Allow specifying a local infra_image under docker config in order to avoid pulling the image.
Use-cases
For my current usecase, I would like to avoid having nomad reach out to pull images at all if possible, so I was hoping to use a local version of the infra image instead of Nomad pulling it.
I can see from the code that right now its always trying to pull the infra_image when setting up the network, and you cant specify a local image like you can for task images.
The text was updated successfully, but these errors were encountered: