You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are errors in the configuration of this machine. Please fix
the following errors and try again:
vm:
* Forwarded port '80' (host port) is declared multiple times
with the protocol 'tcp'.
Steps to reproduce
Run vagrant up in the same directory as Vagrantfile
In my understanding there is the host_ip option should be used. And, seem, guest_ip (without it, it will produce the same problem but on the guest side.)
The text was updated successfully, but these errors were encountered:
P.S.
Seem, the method VagrantPlugins::Kernel_V2::VMConfig::validate() is really huge. Can it be refactored?.. If it will be split, it would be easier to overwrite code parts.
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
In a nutshell, there is no ability to forward the same port of different IP addresses to a guest OS.
E.g.:
Host 127.0.0.111:80 => guest 8011
Host 127.0.0.222:80 => guest 8022
Vagrant version
1.8.6
Host operating system
Windows 10
Guest operating system
CentOS
Vagrantfile
Expected behavior
Added ports forwarding as expected:
Actual behavior
Error output
Steps to reproduce
vagrant up
in the same directory asVagrantfile
References
I have found the code which responsible for this:
https://github.com/mitchellh/vagrant/blob/7eb1091a7102dd4d2ebab762ee1658689a889880/plugins/kernel_v2/config/vm.rb#L688
In my understanding there is the
host_ip
option should be used. And, seem, guest_ip (without it, it will produce the same problem but on the guest side.)The text was updated successfully, but these errors were encountered: