Distributor ID: Ubuntu
Description: Ubuntu 16.04.6 LTS
Release: 16.04
Codename: xenial
Output of the command:
$ minikube start
o minikube v0.35.0 on linux (amd64)
Creating virtualbox VM (CPUs=2, Memory=2048MB, Disk=20000MB) ...
@ Downloading Minikube ISO ...
184.42 MB / 184.42 MB [============================================] 100.00% 0s
! Unable to start VM: create: precreate: VirtualBox is configured with multiple host-only adapters with the same IP "192.168.99.1". Please remove one
$ minikube logs
! api load: filestore: Docker machine "minikube" does not exist. Use "docker-machine ls" to list machines. Use "docker-machine create" to add a new one.
Did you try addressing the configuration issue ?
VirtualBox is configured with multiple host-only adapters with the same IP "192.168.99.1". Please remove one
Thank you. You are right. I used the VirtualBox tool to remove all the dangling host virtual adapters then it worked. I noticed that these virboxnet# interfaces are left over after "minikube delete" . The delete command removed the vms but didn't clean up the interfaces. I repeated a couple of times of start and delete, the virtual interfaces that created by minikube always left there without cleanup.
@gitpop I am curious, are you running this on a cloud VM ? like compute engine ?
@gitpop would this help ?
vboxmanage list -l hostonlyifs | grep 192.168.99.1 -5 | grep -w "Name:" | awk '{$1=""; print $0}'
and remove each returned vboxnet
vboxmanage hostonlyif remove INSERTNAME
I confirm this issue exists, on the virtualbox test box we have more than 21 left over adapters
vboxmanage list -l hostonlyifs | grep -w "Name:" | awk '{$1=""; print $0}'
vboxnet21
vboxnet19
vboxnet12
vboxnet20
vboxnet18
vboxnet7
vboxnet1
vboxnet10
vboxnet14
vboxnet6
vboxnet15
vboxnet9
vboxnet8
vboxnet17
vboxnet16
vboxnet5
vboxnet3
vboxnet13
vboxnet2
vboxnet4
vboxnet11
vboxnet0
or if you want it in one command, one important thing I noticed, you have to deleted it with the same user that runs minikube.
vboxmanage list -l hostonlyifs | grep 192.168.99.1 -5 | grep -w "Name:" | awk '{$1=""; print $0}' | xargs -l vboxmanage hostonlyif remove
Remove one of the boxes with the same IP address, that will solve this problem.
Closing as there is a workaround.
Most helpful comment
@gitpop would this help ?
and remove each returned vboxnet
vboxmanage hostonlyif remove INSERTNAMEI confirm this issue exists, on the virtualbox test box we have more than 21 left over adapters