-
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
Not able to start minikube #20224
Comments
/kind support |
/os windows |
Dear All, I have the same symthom, however I use Virtualbox on top of a Win desktop: zenner@zenner-VirtualBox: ❌ Exiting due to HOST_VIRT_UNAVAILABLE: Failed to start host: creating host: create: precreate: This computer doesn't have VT-X/AMD-v enabled. Enabling it in the BIOS is mandatory zenner@zenner-VirtualBox:~$ However as you see the VT-X/AMD-v is enabled on the VTB VM Could you please advise the way forward? |
zenner@zenner-VirtualBox:~$ minikube start --driver=docker 💣 Exiting due to PROVIDER_DOCKER_NEWGRP: "docker version --format -:" exit status 1: permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Get "http://%2Fvar%2Frun%2Fdocker.sock/v1.47/version": dial unix /var/run/docker.sock: connect: permission denied zenner@zenner-VirtualBox:~$ sudo usermod -aG docker $USER && newgrp docker So it got solved |
What Happened?
PS C:\Windows\system32> minikube start
E0109 15:02:51.427627 2824 start.go:812] api.Load failed for minikube: filestore "minikube": Docker machine "minikube" does not exist. Use "docker-machine ls" to list machines. Use "docker-machine create" to add a new one.
! StartHost failed, but will try again: creating host: create: precreate: This computer doesn't have VT-X/AMD-v enabled. Enabling it in the BIOS is mandatory
X Exiting due to HOST_VIRT_UNAVAILABLE: Failed to start host: creating host: create: precreate: This computer doesn't have VT-X/AMD-v enabled. Enabling it in the BIOS is mandatory
I have also checked and found that virtualization is enabled in BIOS
Attach the log file
logs.txt
Operating System
None
Driver
None
The text was updated successfully, but these errors were encountered: