Unable to start minikube

[Viconz]

What Happened?

C:\Windows\system32>minikube delete

• Removed all traces of the "minikube" cluster.

C:\Windows\system32>minikube start

• minikube v1.31.2 on Microsoft Windows 10 Pro 10.0.19044.2130 Build 19044.2130
• Automatically selected the virtualbox driver
• Starting control plane node minikube in cluster minikube
• Creating virtualbox VM (CPUs=2, Memory=2200MB, Disk=20000MB) ...
  ! StartHost failed, but will try again: creating host: create: precreate: VirtualBox is configured with multiple host-only adapters with the same name "HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter Support mounting host directories into pods #2". Please remove one
• Creating virtualbox VM (CPUs=2, Memory=2200MB, Disk=20000MB) ...
• Failed to start virtualbox VM. Running "minikube delete" may fix it: creating host: create: precreate: VirtualBox is configured with multiple host-only adapters with the same name "HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter Support mounting host directories into pods #2". Please remove one

X Exiting due to GUEST_PROVISION: error provisioning guest: Failed to start host: creating host: create: precreate: VirtualBox is configured with multiple host-only adapters with the same name "HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter #2". Please remove one
*

Attach the log file

C:\Windows\system32>minikube delete

• Removed all traces of the "minikube" cluster.

C:\Windows\system32>minikube start

• minikube v1.31.2 on Microsoft Windows 10 Pro 10.0.19044.2130 Build 19044.2130
• Automatically selected the virtualbox driver
• Starting control plane node minikube in cluster minikube
• Creating virtualbox VM (CPUs=2, Memory=2200MB, Disk=20000MB) ...
  ! StartHost failed, but will try again: creating host: create: precreate: VirtualBox is configured with multiple host-only adapters with the same name "HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter Support mounting host directories into pods #2". Please remove one
• Creating virtualbox VM (CPUs=2, Memory=2200MB, Disk=20000MB) ...
• Failed to start virtualbox VM. Running "minikube delete" may fix it: creating host: create: precreate: VirtualBox is configured with multiple host-only adapters with the same name "HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter Support mounting host directories into pods #2". Please remove one

X Exiting due to GUEST_PROVISION: error provisioning guest: Failed to start host: creating host: create: precreate: VirtualBox is configured with multiple host-only adapters with the same name "HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter #2". Please remove one
*

Operating System

Windows

Driver

VirtualBox

[kundan2707]

/kind support

[spowelljr]

Hi @Viconz, as per the error message, have you tried removing one the of the Ethernet adapters?

VirtualBox is configured with multiple host-only adapters with the same name "HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter https://github.com/kubernetes/minikube/issues/2". Please remove one

[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

[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/test-infra repository.