minishift: [0.3.0] Stuck on Windows 10 and VirtualBox

minishift 0.3.0 Windows 10 64-bit VirtualBox 5.0.26

Stuck at:

>minishift-windows-amd64.exe start --cpus=2 --memory=4096 --vm-driver=virtualbox
Starting local OpenShift cluster...

minishift_vbox_console

Initially it did not work but showed that openshift start had been attempted in the VM. minishift start finished and said to connect to http://192.168.99.100:8433. That redirected to a 10.x.x.x address and didn’t work.

After I disabled firewall and anti-virus (Kaspersky), it got to the state I’m reporting in this issue where minishift start --cpus=2 --memory=4096 --vm-driver=virtualbox does not finish (in 5-10min at least).

About this issue

Original URL
State: closed
Created 8 years ago
Comments: 20 (13 by maintainers)

Most upvoted comments

@gtirloni No need for tears, the future can only get better 😜

jimmidyson on Aug 24, 2016

@jimmidyson unfortunately vagrant is a bit part of our workflow and its support for vmware is on a best effort basis (even with the paid plugin). that’s basically why i’m stuck with virtualbox. i do have a license for vmware workstation that i barely use which makes me sad (its 3d acceleration is awesome).

gtirloni on Aug 24, 2016

Fixed in #56 - will merge & then release 0.4.1

jimmidyson on Aug 24, 2016