Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
--insecure-registry vs. virtualbox IP #461
I just encountered a chicken-and-egg problem with minikube.
I've been starting minikube with the command
I'm having trouble figuring out a way to predict the registry address so I can use it as an argument to --insecure-registry. One way might be to use a nameserver within minikube but I'd need to reconfigure the minikube VM to use it for name resolution.
Is my only option to create a self-signed cert and drop the insecure registry option? Am I missing a more obvious approach?
Thanks in advance.
This is beyond the scope of my understanding of Docker networking but I'm not sure how to teach the registry to bind to localhost on the VM and if kubernetes can pull from localhost.
Hmm, I can think of a few ideas. You could run it with
Then you could create a NodePort load balancer to make it available over localhost.
@dlorenc thanks, the add-on worked perfectly. Here's the config I used: