Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Ubuntu 16.10: No guest IP was given to the Vagrant core NFS helper. #387
Have tried with stock vagrant, virtualbox packages that come with Ubuntu 16.10 via
If I do
The VM should be getting a hostname and I should be able to get my local dev loaded on the browser.
The VM does not get a hostname
Steps to reproduce
@klonos this issue is usually due to a race condition with the
Generally, for better stability I'd recommend setting a static IP, which can be anything that doesn't conflict with your local network eg.
in config.yml set
@thom8 sorry for the late reply, I somehow missed your previous comment. I actually needed to get my environment up and running so I gave up on Ubuntu and set it up on Mac. Will return to this issue to do more testing most likely this weekend when I have time. I'll post back here to let you know how it goes, but the point is to eventually get DHCP working so that config tweaking is kept to a minimum.
@klonos no worries, I think this is unfortunately an upstream issue - https://www.google.com/search?q=No+guest+IP+was+given+to+the+Vagrant+core+NFS+helper&oq=No+guest+IP+was+given+to+the+Vagrant+core+NFS+helper&aqs=chrome..69i57j69i61j69i59j69i61l2.1059j0j7&sourceid=chrome&ie=UTF-8
however possibly isolated to
Let me know if you find a more stable default configuration, I prefer not adding extra config but a static IP also means less conflicts with updating the hosts file & NFS exports.
Yep, will do. We are using beetbox and onboarding was sort of hell because of this (took me so many days trying to figure this out, which made me feel the stupidest I've ever felt in my life - not to mention having to switch to Mac OS). If I get to the bottom of this, I'll be updating our documentation for people that use latest Ubuntu as their local dev env (host OS).
Thanx for this project. A true time saver (...when one gets it to work that is)