Skip to content
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

Open
Dhananjai0209 opened this issue Jan 9, 2025 · 4 comments
Open

Not able to start minikube #20224

Dhananjai0209 opened this issue Jan 9, 2025 · 4 comments
Labels
kind/support Categorizes issue or PR as a support question.

Comments

@Dhananjai0209
Copy link

What Happened?

PS C:\Windows\system32> minikube start

  • minikube v1.34.0 on Microsoft Windows 11 Enterprise 10.0.22621.4602 Build 22621.4602
    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.
  • Using the virtualbox driver based on existing profile
  • Starting "minikube" primary control-plane node in "minikube" cluster
  • Creating virtualbox VM (CPUs=2, Memory=3900MB, Disk=20000MB) ...
    ! 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
  • Creating virtualbox VM (CPUs=2, Memory=3900MB, Disk=20000MB) ...
  • Failed to start virtualbox VM. Running "minikube delete" may fix it: 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

@kundan2707
Copy link
Contributor

/kind support

@k8s-ci-robot k8s-ci-robot added the kind/support Categorizes issue or PR as a support question. label Jan 16, 2025
@kundan2707
Copy link
Contributor

kundan2707 commented Jan 16, 2025

/os windows

@Zenner2
Copy link

Zenner2 commented Jan 22, 2025

Dear All,

I have the same symthom, however I use Virtualbox on top of a Win desktop:

zenner@zenner-VirtualBox:$ minikube delete
💀 Removed all traces of the "minikube" cluster.
zenner@zenner-VirtualBox:
$ minikube start
😄 minikube v1.35.0 on Ubuntu 24.04
✨ Automatically selected the virtualbox driver
👍 Starting "minikube" primary control-plane node in "minikube" cluster
🔥 Creating virtualbox VM (CPUs=2, Memory=4900MB, Disk=20000MB) ...
🤦 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
🔥 Creating virtualbox VM (CPUs=2, Memory=4900MB, Disk=20000MB) ...
😿 Failed to start virtualbox VM. Running "minikube delete" may fix it: creating host: create: precreate: This computer doesn't have VT-X/AMD-v enabled. Enabling it in the BIOS is mandatory

❌ 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
💡 Suggestion: Virtualization support is disabled on your computer. If you are running minikube within a VM, try '--driver=docker'. Otherwise, consult your systems BIOS manual for how to enable virtualization.
🍿 Related issues:
#3900
#4730

zenner@zenner-VirtualBox:~$

However as you see the VT-X/AMD-v is enabled on the VTB VM

Image

Could you please advise the way forward?

@Zenner2
Copy link

Zenner2 commented Jan 22, 2025

zenner@zenner-VirtualBox:~$ minikube start --driver=docker
😄 minikube v1.35.0 on Ubuntu 24.04
✨ Using the docker driver based on user configuration

💣 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
💡 Suggestion: Add your user to the 'docker' group: 'sudo usermod -aG docker $USER && newgrp docker'
📘 Documentation: https://docs.docker.com/engine/install/linux-postinstall/

zenner@zenner-VirtualBox:~$ sudo usermod -aG docker $USER && newgrp docker
[sudo] password for zenner:
zenner@zenner-VirtualBox:$ minikube delete
🙄 "minikube" profile does not exist, trying anyways.
💀 Removed all traces of the "minikube" cluster.
zenner@zenner-VirtualBox:
$
zenner@zenner-VirtualBox:$
zenner@zenner-VirtualBox:
$
zenner@zenner-VirtualBox:$ minikube start --driver=docker
😄 minikube v1.35.0 on Ubuntu 24.04
✨ Using the docker driver based on user configuration
📌 Using Docker driver with root privileges
👍 Starting "minikube" primary control-plane node in "minikube" cluster
🚜 Pulling base image v0.0.46 ...
🔥 Creating docker container (CPUs=2, Memory=4900MB) ...
🐳 Preparing Kubernetes v1.32.0 on Docker 27.4.1 ...
▪ Generating certificates and keys ...
▪ Booting up control plane ...
▪ Configuring RBAC rules ...
🔗 Configuring bridge CNI (Container Networking Interface) ...
🔎 Verifying Kubernetes components...
▪ Using image gcr.io/k8s-minikube/storage-provisioner:v5
🌟 Enabled addons: storage-provisioner, default-storageclass
🏄 Done! kubectl is now configured to use "minikube" cluster and "default" namespace by default
zenner@zenner-VirtualBox:
$

So it got solved

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/support Categorizes issue or PR as a support question.
Projects
None yet
Development

No branches or pull requests

4 participants