-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
don't use the default bridge network list as it's problematic #262
Comments
when vagrant up get stuck at network settings, we have this workaround: adjust the vagrant_config_override.json with the following settings (clean the network interface list): {
"vm": {
"networks": [{
"_id": "0",
"bridge": []
}]
}
} and |
related: hashicorp/vagrant#655 |
this is very critical now, I see lots of problems come from the bride list, let's remove the list, make users to choose manually first. |
this is problematic when:
|
so the new behavior follows:
for example:
|
@ #262 | don't use the default bridge network list as it's problematic
the list is not correct for many cases, we should find a way for auto select precisely.
The text was updated successfully, but these errors were encountered: