not able to start minikube using docker driver

[jai-tom]

What Happened?

I installed docker first.
Then downloaded minikube exe file and added the path as well.
when tried to start the minikube using docker as driver error occurred.
Tried multiple times.
Tried the minikube delete command as well.

Attach the log file

minikube start
😄 minikube v1.32.0 on Microsoft Windows 11 Home Single Language 10.0.22631.2715 Build 22631.2715
✨ Automatically selected the hyperv driver
👍 Starting control plane node minikube in cluster minikube
🔥 Creating hyperv VM (CPUs=2, Memory=2200MB, 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=2200MB, Disk=20000MB) ...
😿 Failed to start hyperv VM. Running "minikube delete" may fix it: creating host: create: precreate: Hyper-V PowerShell Module is not available

❌ Exiting due to PR_HYPERV_MODULE_NOT_INSTALLED: Failed to start host: creating host: create: precreate: Hyper-V PowerShell Module is not available
💡 Suggestion: Run: 'Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V-Tools-All -All'
📘 Documentation: https://www.altaro.com/hyper-v/install-hyper-v-powershell-module/
🍿 Related issue: #9040

Operating System

Windows

Driver

Docker

[pnasrat]

Note it looks like you are still trying to start with the hyper-v driver. Please can you do the following steps and see if minikube starts with the docker driver successfully

• If using WSL2and docker follow the linked instructions at https://minikube.sigs.k8s.io/docs/tutorials/wsl_docker_driver/
• minikube stop
• minikube delete --purge --all
• Ensure docker is running and test by doing docker run -ti --rm alpine echo hello docker runs and prints hello docker from your windows shell/powershell
• run minikube start --driver=docker

/kind support
/triage needs-information

[k8s-triage-robot]

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]

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

[Ritikaa96]

Hi Are you able to follow these steps ? If they solve this issue please close it using /close

Note it looks like you are still trying to start with the hyper-v driver. Please can you do the following steps and see if minikube starts with the docker driver successfully

• If using WSL2and docker follow the linked instructions at https://minikube.sigs.k8s.io/docs/tutorials/wsl_docker_driver/
• minikube stop
• minikube delete --purge --all
• Ensure docker is running and test by doing docker run -ti --rm alpine echo hello docker runs and prints hello docker from your windows shell/powershell
• run minikube start --driver=docker

/kind support /triage needs-information

[k8s-triage-robot]

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

This bot triages 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:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

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

/close not-planned

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

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

This bot triages 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:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

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

/close not-planned

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.