Error during Minikube Environment Setup (minikube start)

bhuvana-ssk commented 4 months ago

What Happened?

While running the minikube start command, I am repeatedly getting this issue. Even I have tried uninstall and reinstalling minikube, even after that I am getting this error.

Even I can see the container running in the Rancher Desktop [Container in Rancher Desktop] Screenshot 2024-07-10 124551

The minikube status is [Minikube Status] Screenshot 2024-07-10 131107

Feel free to ask any other details, if necessary.

I have to setup the minikube environment and deploy my docker image into minikube.


**C:\Windows\System32>minikube start
* minikube v1.33.1 on Microsoft Windows 11 Pro For Workstations 10.0.22631.3737 Build 22631.3737
* Automatically selected the docker driver. Other choices: hyperv, ssh
* Using Docker Desktop driver with root privileges
* Starting "minikube" primary control-plane node in "minikube" cluster
* Pulling base image v0.0.44 ...
* Downloading Kubernetes v1.30.0 preload ...
    > preloaded-images-k8s-v18-v1...:  342.90 MiB / 342.90 MiB  100.00% 370.04
    > gcr.io/k8s-minikube/kicbase...:  481.58 MiB / 481.58 MiB  100.00% 452.04
* Creating docker container (CPUs=2, Memory=10100MB) ...
* Stopping node "minikube"  ...
* Powering off "minikube" via SSH ...
* Deleting "minikube" in docker ...
! StartHost failed, but will try again: creating host: create host timed out in 360.000000 seconds
* Creating docker container (CPUs=2, Memory=10100MB) ...
* Failed to start docker container. Running "minikube delete" may fix it: creating host: create host timed out in 360.000000 seconds
! Startup with docker driver failed, trying with alternate driver hyperv: Failed to start host: creating host: create host timed out in 360.000000 seconds
* Deleting "minikube" in docker ...
* Deleting container "minikube" ...
* Removing C:\Users\bhuvana.s\.minikube\machines\minikube ...
! Failed to delete cluster minikube, proceeding with retry anyway.
* Downloading VM boot image ...
    > minikube-v1.33.1-amd64.iso....:  65 B / 65 B [---------] 100.00% ? p/s 0s
    > minikube-v1.33.1-amd64.iso:  314.16 MiB / 314.16 MiB  100.00% 865.41 KiB
* Starting "minikube" primary control-plane node in "minikube" cluster
* Creating hyperv VM (CPUs=2, Memory=6000MB, Disk=20000MB) ...
! StartHost failed, but will try again: creating host: create: precreate: Hyper-V PowerShell Module is not available
* Creating hyperv VM (CPUs=2, Memory=6000MB, Disk=20000MB) ...
* Failed to start hyperv VM. Running "minikube delete" may fix it: creating host: create: precreate: Hyper-V PowerShell Module is not available

X Exiting due to DRV_CREATE_TIMEOUT: Failed to start host: creating host: create host timed out in 360.000000 seconds
* Suggestion: Try 'minikube delete', and disable any conflicting VPN or firewall software
* Related issue: https://github.com/kubernetes/minikube/issues/7072**

Attach the log file

logs.txt

Operating System

Windows

Driver

Docker

kundan2707 commented 4 months ago

/kind support

kundan2707 commented 4 months ago

Please try and share

minikube delete --all --purge
minikube start

k8s-triage-robot commented 1 month ago

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

After 90d of inactivity, lifecycle/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

Mark this issue as fresh with /remove-lifecycle stale
Close this issue with /close
Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot commented 2 weeks ago

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

After 90d of inactivity, lifecycle/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

Mark this issue as fresh with /remove-lifecycle rotten
Close this issue with /close
Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

kubernetes / minikube