$ minikube --vm-driver=xhyve start --show-libmachine-logs --v=5
Starting local Kubernetes cluster...
Running pre-create checks...
Creating machine...
(minikubeVM) Downloading /Users/pires/.minikube/cache/boot2docker.iso from https://storage.googleapis.com/minikube/minikube-0.5.iso...
(minikubeVM) 0%....10%....20%....30%....40%....50%....60%....70%....80%....90%....100%
(minikubeVM) Creating VM...
(minikubeVM) Extracting vmlinuz64 and initrd.img from boot2docker.iso...
(minikubeVM) Waiting for VM to come online...
(minikubeVM) Waiting on a pseudo-terminal to be ready... Hook up a terminal emulator to /dev/ttys002 in order to access your VM
(minikubeVM) Waiting for VM to come online...
(minikubeVM) Waiting on a pseudo-terminal to be ready... Hook up a terminal emulator to /dev/ttys002 in order to access your VM
(minikubeVM) done
(minikubeVM) Hook up your terminal emulator to /dev/ttys002 in order to connect to your VM
E0710 00:57:51.743872 85042 start.go:70] Error starting host: Error starting stopped host: Machine didn't return an IP after 120 seconds, aborting
Note that /dev/ttys002 doesn't exist.
$ brew info docker-machine-driver-xhyve
docker-machine-driver-xhyve: stable 0.2.2 (bottled), HEAD
$ ls -las $(brew --prefix)/opt/docker-machine-driver-xhyve/bin/docker-machine-driver-xhyve
27392 -r-sr-xr-x 1 root wheel 14022496 Jan 22 01:55 /usr/local/opt/docker-machine-driver-xhyve/bin/docker-machine-driver-xhyve
$ sw_vers
ProductName: Mac OS X
ProductVersion: 10.11.5
BuildVersion: 15F34
It looks like the brew installer doesn't set the permissions correctly on the docker-machine-driver-xhyve binary. Can you try the sudo chmod/chown commands here:
https://github.com/zchee/docker-machine-driver-xhyve/releases
(but switch it to your location)
Setting the correct perms as described in the brew into output fixed this for me :)
Perhaps we can add some validation of the plugin binary & give more feedback to user if they hit this?
Yeah we should do that before #270.
I have followed the suggestions but minikube can't be started with xhyve on MacOS
brew install docker-machine-driver-xhyve
==> Downloading https://homebrew.bintray.com/bottles/docker-machine-driver-xhyve-0.2.2.el_capitan.bottle.1.tar.gz
Already downloaded: /Users/chmoulli/Library/Caches/Homebrew/docker-machine-driver-xhyve-0.2.2.el_capitan.bottle.1.tar.gz
==> Pouring docker-machine-driver-xhyve-0.2.2.el_capitan.bottle.1.tar.gz
==> Caveats
This driver requires superuser privileges to access the hypervisor. To
enable, execute
sudo chown root:wheel $(brew --prefix)/opt/docker-machine-driver-xhyve/bin/docker-machine-driver-xhyve
sudo chmod u+s $(brew --prefix)/opt/docker-machine-driver-xhyve/bin/docker-machine-driver-xhyve
==> Summary
馃嵑 /usr/local/Cellar/docker-machine-driver-xhyve/0.2.2: 2 files, 13.4M
dabou-macosx:~/Temp/minikube$ ll $(brew --prefix)/opt/docker-machine-driver-xhyve/bin/docker-machine-driver-xhyve
-r-xr-xr-x 1 chmoulli admin 14022496 Jan 22 02:55 /usr/local/opt/docker-machine-driver-xhyve/bin/docker-machine-driver-xhyve
dabou-macosx:~/Temp/minikube$ chmod +x /usr/local/opt/docker-machine-driver-xhyve/bin/docker-machine-driver-xhyve
dabou-macosx:~/Temp/minikube$ sudo chown root:wheel /usr/local/opt/docker-machine-driver-xhyve/bin/docker-machine-driver-xhyve
Password:
dabou-macosx:~/Temp/minikube$ sudo chmod u+s /usr/local/opt/docker-machine-driver-xhyve/bin/docker-machine-driver-xhyve
dabou-macosx:~/Temp/minikube$ ll $(brew --prefix)/opt/docker-machine-driver-xhyve/bin/docker-machine-driver-xhyve
-r-sr-xr-x 1 root wheel 14022496 Jan 22 02:55 /usr/local/opt/docker-machine-driver-xhyve/bin/docker-machine-driver-xhyve
dabou-macosx:~/Temp/minikube$ minikube --vm-driver=xhyve start --show-libmachine-logs --v=5
Starting local Kubernetes cluster...
(minikubeVM) Waiting for VM to come online...
(minikubeVM) Waiting for VM to come online...
(minikubeVM) Waiting for VM to come online...
E0715 09:23:46.619917 45279 start.go:74] Error starting host: Error starting stopped host: Machine didn't return an IP after 120 seconds, aborting
Mac Version
sw_vers
ProductName: Mac OS X
ProductVersion: 10.11.5
BuildVersion: 15F34
@cmoulliard do you have VBox installed and eventually VMs running already, i.e. boot2docker?
Virtualbox is installed but not running. I'm using docker-machine and not longer boot2docker
@cmoulliard but docker-machine with Virtualbox uses a boot2docker.iso under the hoods. Could you fire up your VirtualBox UI and ensure that not VM is running ?
I remember darkly that I had a similar issue yesterday.
No VM is running within VirtualBox when I launch minikube
Just retried it in various combinations (create a VBox VM, stopped it, created then a xhyve VM, ...), everything works like expected with 0.6.0 ;-(
Been able to boot the VM after many attempts.
We should look into making this more reliable.
We see this failure sometimes in our CI test runs.
rm /Users/.../.minikube folder,rerun start will work
I have had a similar issue (Machine didn't return an IP after 120 seconds) after an unsuccessful installation of fabric8 (0.4.72) on minikube (0.10.0). Removing the .minikube folder AND issuing a minikube delete seeme to have done the trick.
I think the @zchee has fixed a bunch of these issues in later xhyve-driver releases. Please re-open if you're still seeing this.
Saw it just by now. Definitely had the permissions on xhyve driver set up correctly and everything. The only thing that helped out was:
`sudo rm -rf .minikube `
And retry:
`gofabric8 start`
Most helpful comment
Perhaps we can add some validation of the plugin binary & give more feedback to user if they hit this?