-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
[VBOX_NOT_FOUND] create: precreate: VBoxManage not found #4117
Comments
@kevinsingapore looks like you are missing config.json file from your docker installation. Try Reinstalling the docker and then run the minikube again. |
on linux you don't need to use default virtualbox driver. You can use kvm2 or none driver types. |
@kevinsingapore - Please install Virtualbox, which is what the "advice" section is trying to convey. Do you have a recommendation on how I could improve the error message? |
envirorment: kvm manchine
os : centos7.5
when use "./minikube start", errors as follows:
`o minikube v1.0.0 on linux (amd64)
$ Downloading Kubernetes v1.14.0 images in the background ...
2019/04/19 00:59:30 Unable to read "/root/.docker/config.json": open /root/.docker/config.json: no such file or directory
2019/04/19 00:59:30 No matching credentials were found, falling back on anonymous
2019/04/19 00:59:30 Unable to read "/root/.docker/config.json": open /root/.docker/config.json: no such file or directory
2019/04/19 00:59:30 No matching credentials were found, falling back on anonymous
2019/04/19 00:59:30 Unable to read "/root/.docker/config.json": open /root/.docker/config.json: no such file or directory
2019/04/19 00:59:30 No matching credentials were found, falling back on anonymous
! Unable to start VM
X Error: [VBOX_NOT_FOUND] create: precreate: VBoxManage not found. Make sure VirtualBox is installed and VBoxManage is in the path
i Advice: Install VirtualBox, ensure that VBoxManage is executable and in path, or select an alternative value for --vm-driver
i want to get some help, how to deal with it?
The text was updated successfully, but these errors were encountered: