-
Notifications
You must be signed in to change notification settings - Fork 34
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
Temporary Error: Could not find an IP address for #12
Comments
Having a similar problem: works with minikube but not with docker machine. Driving me nuts. |
@nomasprime I haven't found any solution... Probably the best option to switch to Linux or run the whole stuff in Linux VM... |
@zoltan-nz thanks for letting me know. I've only just started playing around with this stuff so no clue and a bit concerned that this project doesn't seem to have much support. Docker for Mac seems to work OK so I'm wondering what the difference is between the two. |
@nomasprime you can find my notes in the following repositories' README, I played a little bit with these tools to find out which could be a smooth solution for research projects or for teaching, practicing... https://github.com/zoltan-nz/playing-with-openshift Maybe try out these steps: https://github.com/zoltan-nz/playing-with-kubernetes#minikube |
Hi Team, thanks for your hard work.
I'm playing with
minikube
,minishift
anddocker-machine
. Mainly withhyperkit
driver.Following the official instructions
minikube
andminishift
starts without any problem. They can get proper IP numbers also, so almost everything right.Environment: macOS Mojave 10.14.4
I just wanted to create a
default
docker-machine with hyperkit and I get the following error all the time, doesn't matter how I try it.I tried with and without
dnsmasq
also. Always get the same error.I tried with and without
IPAddress
and with and withoutCmdline
.Default's
config.json
:This is the
minikube
'sconfig.json
. It works like a charm.Hope there is some trick what I can try to launch a default docker machine. Thanks. :)
The text was updated successfully, but these errors were encountered: