VirtualBox is configured with multiple host-only adapters with the same name "HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter". Please remove one
daihanhle opened this issue · 2 comments
What Happened?
PS C:\minikube> .\minikube start --vm-driver="virtualbox"
- minikube v1.24.0 on Microsoft Windows 10 Home 10.0.19042 Build 19042
- Using the virtualbox driver based on user configuration
- Starting control plane node minikube in cluster minikube
- Creating virtualbox VM (CPUs=2, Memory=4000MB, 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". Please remove one - Creating virtualbox VM (CPUs=2, Memory=4000MB, 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". Please remove one
X Exiting due to GUEST_PROVISION: 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". Please remove one
*
╭─────────────────────────────────────────────────────────────────────────────────────────────╮
│ │
│ * If the above advice does not help, please let us know: │
│ https://github.com/kubernetes/minikube/issues/new/choose │
│ │
│ * Please run minikube logs --file=logs.txt
and attach logs.txt to the GitHub issue. │
│ │
╰─────────────────────────────────────────────────────────────────────────────────────────────╯
Attach the log file
Operating System
Windows
Driver
VirtualBox
Hi @daihanhle, thanks for reporting your issue with minikube!
I found a StackOverflow post that looks related to your issue, can you take a look at let me know if that solves your problem, thanks!
Hi @daihanhle, we haven't heard back from you, do you still have this issue?
There isn't enough information in this issue to make it actionable, and a long enough duration has passed, so this issue is likely difficult to replicate.
I will close this issue for now but feel free to reopen when you feel ready to provide more information.