Open tcataldo opened 6 years ago
I'm experiencing the same thing.
This has to do with a behavior change in the VMware plugin itself... I noticed it a while back too.
https://github.com/hashicorp/vagrant/issues/9151
This is hack to keep it from getting in the way for now...
config.hostmanager.ip_resolver = proc do |vm, resolving_vm|
if vm.id && vm.provider_name == :vmware_fusion
`'/Applications/VMware Fusion.app/Contents/Library/vmrun' getGuestIPAddress "#{vm.id}" -wait`.chomp
end
end
Adding -wait
to the vmrun command seems to have eliminated the issue on first boot.
@bdwyertech your solution works great for me. Thanks!
I may have gotten it working. More tomorrow.
Cheers,
JP
On Dec 18, 2017, at 5:14 PM, Brian Dwyer notifications@github.com wrote:
This has to do with a behavior change in the VMware plugin itself... I noticed it a while back too.
hashicorp/vagrant#9151
— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.
The same is happening to me with docker on version 2.0.2 , are you sure this is VMware related only issue? I could be messing something up.
Just adding this issue is not only vmware related as I asked before and is vagrant version related https://github.com/devopsgroup-io/vagrant-hostmanager/issues/257
I've the same issue if I enable dhcp instead of static IP
config.vm.network "private_network", type: "dhcp"
Tried playing with hostmanager options without success.
according to documentation as referenced in an official reply
setting v.ssh_info_public = true
would solve the problem
The real ip (obtained from vmware dhcp) was assigned correctly with previous version. example VagrantFile: