Thanks a lot Alvaro
that works fine.
I've read the doc and the ebook 'Vagrant Up and Running" but I didn't find
this configuration option
Have a nice day
Bruno
Le mercredi 12 octobre 2016 18:50:16 UTC+2, Alvaro Miranda Aguilera a
écrit :
>
> hello
>
> Vagrant doesn't create the network,
Hi all. Novice here. I'm trying to install VVV for the first time. The
installation completed, but with prohibitive errors. Before I fix them, I
want to first completely uninstall VVV from my system (Win 10, x64). To do
so, I ran these commands:
- vagrant destroy
- vagrant box
hello
Vagrant doesn't create the network, its VirtualBox.
Try this:
Vagrant.configure(2) do |config|
config.vm.box = "hashicorp/precise64"
config.vm.provider "virtualbox" do |v|
v.customize ["modifyvm", :id, "--natnet1", "10.0.3/24"]
end
end
Alvaro.
On Wed, Oct 12, 2016 at
Hello
when I create a new VM with vagrant for VirtualBox, Vagrant create a
forwarded port 22 -> in subnet 10.0.2.0/24. it is a problem for me
since 10.0.2.0/16 is already is the current subnet of my local network
Is there a way/parameter to change the subnet in which the first network
Hello,
I am using using/trusty64
Output of vagrant up
$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Clearing any previously set forwarded ports...
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces
Hi Ian,
Excellent News!
Best regards,
Gilles
Le mercredi 12 octobre 2016 10:13:16 UTC+2, Ian Smith a écrit :
>
> Hi Gilles,
>
> Sorry error between chair and keyboard this time. Now that the override
> file is being read there was an ansible_ssh_host line in the override file
> which overrode
Hi Gilles,
Sorry error between chair and keyboard this time. Now that the override
file is being read there was an ansible_ssh_host line in the override file
which overrode the Vagrant generated one in the inventory. Removing that
line now means that the deployment now completes.
Many thanks
Hi Gilles,
Thank you for that tip. I can see that the override file is now being used
as expected. However the problem is now that the override server name is
correctly being used the initial vagrant ssh connection to create the user
is attempting to connect to the IP address of the server not
Hello
If you can share the name of the box. and a gist of the output of vagrant
up I can help.
Some boxes don't have the virtualization driver or they use rsync (for
license issues or some people think rsync is faster/better/etc)
So my suggestion will be test other box too: hashicorp/precise64
