minikube: virtualbox: "The host-only adapter we just created is not visible" (needed reboot)
Is this a BUG REPORT or FEATURE REQUEST? Bug report for misleading error message / request for improved docs & error messages
Please provide the following details:
Environment:
Minikube version : v0.33.1
- OS : macOS Mojave 10.14.2 (18C54)
- VM Driver : VirtualBox 6.0
- ISO version : minikube-v0.33.1.iso
What happened:
minikube start
Starting local Kubernetes v1.13.2 cluster...
Starting VM...
E0131 14:39:29.593152 91186 start.go:205] Error starting host: Error starting stopped host: 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.
Retrying.
E0131 14:39:29.595252 91186 start.go:211] Error starting host: Error starting stopped host: 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
minikube failed :( exiting with error code 1
What you expected to happen:
- minikube to work correctly,
- OR, a helpful error message
How to reproduce it (as minimally and precisely as possible):
- Completely fresh install of VirtualBox & minikube
- Try running
minikube start - See the abovementioned error
NOTE: the relevant workaround / fix is to reboot your machine after you have installed VirtualBox. Yes, even on macOS. This is not mentioned in either the docs or the error message - as a user, I had to dig up GitHub issues to find a reference to this.
It would be super useful to have a) better documentation about this, e.g. in readme quickstart b) better error messages
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Reactions: 7
- Comments: 17 (5 by maintainers)
Just an addition to the @Walther 's comment for the people who are looking for solution to the problem and end up here… Your VirtualBox might have security issues on MacOS. To solve it you should go to Security&Privacy settings and allow VirtualBox. Allow option only visible after the fresh installation of VirtualBox. If you do not see allow button, try removing the VirtualBox via uninstaller then install it again. After that check the Security&Privacy settings, you should be able to see the allow option.
Update: if like me, you have tried to run
minikube startright after a VirtualBox install, without rebooting, the minikube cluster can be in an inconsistent, non-starting state, and not work even after a reboot. But you’ll get a new, different error.This above error has been also reported here https://github.com/kubernetes/minikube/issues/3354
However, after running
minikube deleteandminikube start, I seemed to get into a working state:To wrap up:
minikube start, observe error 1 of “the host-only adapter we just created is not visible”minikube start, observe error 2 of “timed out waiting for the condition”minikube delete,minikube start, observe minikube working correctly.So: running
minikube startafter VirtualBox installation but before rebooting can cause minikube to be in an error state.I got it work by:
Perhaps the error message should be:
“Error starting host: The network adapter is not visible. If you just installed VirtualBox, you may need to reboot it before creating a VM.”
Closing as a workaround was found. minikube will now suggest that the user reinstalls VirtualBox and reboots.
I’m getting the same error on my Debian Linux. So, I started with
minikube start -v 9and get this log:I fixed that loading the missing kernel modules (as root):
No restart or delete required.
Installed Versions:
I got it work by: System Preferences -> Security & Privacy -> Allow -> Then allow the software corporation (in this case Oracle)
I think still have same problem after reboot