-
Notifications
You must be signed in to change notification settings - Fork 7
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
provider base image does not correspond to the minikube default image #101
Comments
This.. is strange👀 - the default value is actually pulled from the cli defaults, so I'm a bit surprised that this is getting switched during runtime. I guess the minikube team have migrated their images over to the github registery. I'll work on a fix now 👍🏼 |
Nvm, seems like a local problem. Some minikube log:
After |
It looks like minikube first looks at the local docker daemon before deciding whether or not to download the image. The mismatch here is that check disregards the host (docker.io vs ghr.io), causing the diff. I'm somewhat tempted to remove the base_image option entirely, as this doesn't seem useful to be set via terraform i.e. playing around with base_image entails debugging of minikube itself |
Describe the bug
provider base image does not correspond to the minikube default image
To Reproduce
tf apply ->
tf apply again ->
Expected behavior
No changes compared to the first tf run.
The text was updated successfully, but these errors were encountered: