Skip to content
This repository has been archived by the owner on Sep 26, 2021. It is now read-only.

VirtualBox is configured with multiple host-only adapters with the same IP #3584

Open
coolbrg opened this issue Jul 16, 2016 · 7 comments
Open

Comments

@coolbrg
Copy link

coolbrg commented Jul 16, 2016

Hi,

I started trying "docker-machine" in linux and hit by the error in the create step. Error

$ docker-machine -v
docker-machine version 0.7.0, build a650a40

$ docker-machine create --driver virtualbox dev
Running pre-create checks...
Error with pre-create check: "VirtualBox is configured with multiple host-only adapters with the same IP \"172.28.128.1\". Please remove one."

Any idea? I have already two VMs in stopped state.

$ VBoxManage list vms                          
"win7" {ade478d8-3080-409b-999f-a32f1cf40797}
"vagrant-service-manager_default_1467614255243_88024" {78929938-435f-4713-bb96-b1b0538494ad}
@coolbrg
Copy link
Author

coolbrg commented Jul 18, 2016

I am getting this issue in Fedora 24. Windows 10 is working fine.

@migaes
Copy link

migaes commented Jan 21, 2017

What this error is telling you is that you have more that one host-only network adapter with the same same IP 172.28.128.1
If you open VirtualBox Panel and go to Settings/Network/Host-only Networks section, you can delete adapaters with duplicated IP addresses.

@030
Copy link

030 commented Jul 13, 2017

@bormansquirrel Thank you. I opened VB and after removing all host-only networks in File>preferences>network>host-only networks, minikube was able to start

@Cryptophobia
Copy link

@bormansquirrel : this issue can happen with minikube as well. thanks for the solution.

@rondinif
Copy link

oc cluster up --create-machine
gave me similar Error with pre-create check: "VirtualBox is configured with multiple host-only adapters with the same IP "192.168.56.1". Please remove one"

searched duplicated hostonly interfaces on 192.168.56.1:
VBoxManage list -l hostonlyifs

found vboxnet0 and vboxnet1 both on 192.168.56.1; deleted only the second one:
VBoxManage hostonlyif remove vboxnet1
now: oc cluster up --create-machine works fine

@Cryptophobia
Copy link

@rondinif , that is a good solution as well. all done through the vboxmanage cli.

@femisystems
Copy link

Thanks @rondinif. I had the same issue and the solution you proffered fixed it.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants