You can define the ip as below in the Vagrant file. It just should not collide with some already used in your sub-network.
config.vm.network "public_network", ip: "192.xxx.xxx.xxx", bridge => "em1" # whatever interface is on the host vagrant-plugin is good one, but I use another approach by connecting the VMs as Jenkins slaves. пятница, 19 июня 2015 г., 7:03:04 UTC+1 пользователь [email protected] написал: > > For bridged network I can update the entry in vagrantfile. > i.e. config.vm.network > > > > On Friday, June 19, 2015 at 11:26:01 AM UTC+5:30, [email protected] wrote: >> >> Hi , >> >> I have installed virtual box, vagrant, jenkins and my goal is to create >> vagrant VM using jenkins job. >> >> I have installed vagrant-jenkin plugin and using the provision vm option >> to create VM but somehow its not working. >> Before running jenkins job I have added base box in vagrant and started >> it using command vagrant up. >> What are the things I am missing ? Any help appreciated. >> >> Also I have observed that IP allocation is different in vagrant vm Vs >> manual virtual box vm. >> Can vagrant VM take IP from same IP range which host machine is ? >> >> Thanks. >> >> -- You received this message because you are subscribed to the Google Groups "Vagrant" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
