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
vagrant up fails with config.vm.network :hostonly #1628
Comments
The new syntax is
I need to do a better job of catching this sort of misuse. |
just went through the same thing, didnt know the syntaxis change |
The |
Why was the syntax changed in the first place? This is causing people pain, I have to rewrite my Vagrant scripts. What was the benefit.? It seems like using Vagrant has gained the pitfalls of 'works for me' problems that it was supposed to solve by precisely defining VMs. Sorry but I just want to get on and debug my actual website code, not debug the tools that setup my LAMP stack i.e Vagrant. |
@therobyouknow If you're unhappy with the new syntax you can stick with the old syntax and it works just fine, just make sure it is in a V1 ( |
@mitchellh - thanks so much for responding, honoured to hear from the creator of Vagrant! Thanks for the V1 tip - that will help, it's appreciated. Though I'd like to move with the times and rework my scripts. I will also update my end-to-end start from scratch setting up Vagrant guide, here: http://stackoverflow.com/a/15067918/227926 |
Hi, I tried the new synxtax. It worked. But I still need 'host-only' network interface, because I need to connect to host network, not between virtual machines internally. I cannot ping from host to guest's internal IP. |
config.vm.network :private_network, ip: "192.168.56.10" that works for me. On Sat, Apr 19, 2014 at 4:45 PM, chrisd notifications@github.com wrote:
|
I mean I don't see my host IP for subnet 192.168.56.0/24 as host-only network as usual. For host-only network, I usually get a IP like 192.168.56.100 for my host. So how would I access to private network of guess without a valid IP. |
in Virtualbox, you have, nat, bridge, private, and host only. can past the line you have in your vagrant file and a screesshot how the network look in Virtualbox gui once the vm is created? |
Vagrant crashing on: top of the stack: I have tried this in different spots of my Vagrantfile. I have tried without the netmask and auto_config false. Always the same. Any clue? |
@muk302 You need to uninstall the vagrant-windows plugin |
I don't remember installing that plugin. Thank you. Now that I look at the path, it all makes sense now. I know...noobs. |
When I run
vagrant up
withconfig.vm.network :hostonly, "33.33.33.33"
I recieve the following error:If I go with
config.vm.network :public_network
everything works fine.Windows 7 x64
Vagrant 1.2.1
Oracle VirtualBox 4.2.12 r84980
The text was updated successfully, but these errors were encountered: