35

I am a beginner to Kubernetes and starting off with this tutorial. I installed VM and expected to be able to start a cluster by using the command: 

minikube start

But I get the error: 

Starting local Kubernetes v1.10.0 cluster...
Starting VM...
E0911 13:34:45.394430   41676 start.go:174] Error starting host: Error 
creating host: Error executing step: Creating VM.
: Error setting up host only network on machine start: The host-only 
adapter we just created is not visible. This is a well known 
VirtualBox bug. You might want to uninstall it and reinstall at least 
version 5.0.12 that is is supposed to fix this issue.

It says that it is a well known bug in Virtualbox but I installed its latest version. Any ideas?

Satyajit Das
  • 2,740
  • 5
  • 16
  • 30

4 Answers4

63

Figured out the issue. VirtualBox was not installed correctly as Mac had blocked it. It wasn't obvious at first.

  • Restarting won't work if VirtualBox isn't installed correctly.

  • System Preferences -> Security & Privacy -> Allow -> Then allow the software corporation (in this case Oracle)

  • Restart

Now it worked as expected.

Satyajit Das
  • 2,740
  • 5
  • 16
  • 30
  • 5
    I don't see any option for 'Allow' – Robeezy Aug 15 '19 at 23:33
  • 1
    If you don't see "Allow" option or even after multiple restarts also if it didn't worked then try to update vmware then follow above steps it will work.it worked for me with VirtualBox-6.0.10-132072-OSX.dmg version – prasad Sep 05 '19 at 03:11
  • 2
    If you don't see "Allow," make sure you're in the "General" tab of Security & Privacy, not any of the other three. – jarhill0 May 01 '20 at 01:53
  • 2
    Using OSX 10.15.6 (catalina) and VirtualBox 6.1.12, I had to use System Preferences, Security and Privacy, General to allow Oracle ("Allow apps downloaded from: App Store and identified developers"). Then I removed and reinstalled VirtualBox. Also try starting a VM from the VirtualBox GUI, that discovered two other permissions that it required. – chrisinmtown Jul 23 '20 at 01:33
  • 1
    This stack overflow page is linked to from the failed output of `minikube start`, but I'd like to point out that running minikube start on kernel 5.8 of fedora core 32 breaks this way too. Going back to kernel 5.7.x fixed this issue for me. – Philthi Sep 09 '20 at 14:25
  • 1
    Thanks , working for me, validated at Mac OS Catalina with VirtualBox-6.1.14 – santosh verma Sep 28 '20 at 12:19
  • I second the comment above. This worked for me too. I didn't see the allow button at first, either. After I clicked the uninstall tool that VirtualBox provided, I saw a button on the general tab under security and privacy. Then I installed 6.1.14 again, and the allow button was present on the General tab, and everything worked from there! – Sankofa Oct 05 '20 at 21:17
7

Have you tried restarting your computer after installing the VirtualBox ? (seems to be also a known bug to docker-machine which is used by minikube to initialize you local env)

Nepomucen
  • 4,449
  • 3
  • 9
  • 24
4

This definitely worked for me, starting minikube by specifying vm-driver and kubernetes-version

minikube start --vm-driver=hyperkit --kubernetes-version v1.16.0

Sandeep
  • 131
  • 1
  • 9
  • 1
    Be aware that this above command is not using a virtualbox driver. Hyperkit is a whole different beast on it's own, with it's own set of features and issues. – Ivan May 12 '20 at 07:49
  • virtual box and docker driver don't work for me on macOS 12.6 intel. hyperkit works! – Tony Lucas Oct 23 '22 at 05:09
3

Faced a similar issue in Mac after upgrading to big sur. The running minikube instance started giving the same error.

The solution that worked for me was to run a minikube delete, followed by a minikube start.

More combination of this option can be found in the thread below -

https://github.com/kubernetes/minikube/issues/3614

RohitG
  • 67
  • 3
  • 10