Skip to content
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

private network adapter 1 borks vm setup. #4429

Closed
gtmtech opened this issue Sep 2, 2014 · 1 comment
Closed

private network adapter 1 borks vm setup. #4429

gtmtech opened this issue Sep 2, 2014 · 1 comment

Comments

@gtmtech
Copy link

gtmtech commented Sep 2, 2014

A note in the vagrant docs would be useful explaining not to configure adapter1 as a private_network otherwise it will bork the NAT adapter (adapter 1) which is essential for vagrant to setup the VM

I.e. this:

VAGRANTFILE_API_VERSION = "2"
Vagrant.configure(VAGRANTFILE_API_VERSION) do |config|
config.vm.box = "hashicorp/precise64"
config.vm.network "private_network", ip: "10.0.2.101", :adapter => 1
end

will never work, but this:

VAGRANTFILE_API_VERSION = "2"
Vagrant.configure(VAGRANTFILE_API_VERSION) do |config|
config.vm.box = "hashicorp/precise64"
config.vm.network "private_network", ip: "10.0.2.101"
end

will work fine as it actually sets up a 2nd adapter.

@mitchellh
Copy link
Contributor

Vagrant requires adapter 1 to be a NAT adapter. This is a limitation of Vagrant that we don't plan on fixing soon since it complicates the bootstrapping problem (how does one SSH reliably without it).

@ghost ghost locked and limited conversation to collaborators Apr 10, 2020
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

2 participants