Not sure if this is a common issue, but I've easily set up a VM with static
IP using the following:
Vagrantfile:
*config.vm.define "swrmsca" do |swrmsca|*
*swrmsca.vm.box = "bento/centos-7.2"*
*swrmsca.vm.network "private_network", ip: "192.168.1.101"*
*swrmsca.vm.hostname = "swrms
Perhaps it's an issue with not understanding Virtualbox, but I'm trying to
create a simple Linux Desktop environment on my Windows 10 system and the
"desktop" never appears (the virtualbox UI is still showing a CLI). I've
posted my Vagrantfile below:
Honestly, I'm open to using any pre-made (d
When I connect into my company VPN (which lives behind a proxy) and do
"vagrant up" on one of my VM's, there is a long delay (couple minutes)
before the:
Bringing machine 'example' up with 'virtualbox' provider...
appears. I'm guessing vagrant tries to do something "networky" and
eventual
wrote:
>
> hello
>
> Ass this and check if helps:
> config.vm.box_check_update = false
>
>
> if not, try to setup verbose logging
>
> set VAGRANT_LOG=debug
>
> or
>
> export VAGRANT_LOG=debug
>
> and do a Vagrant up on vpn
>
> Thanks
> Alvaro
&g
So, I've populated a YAML file and loaded it into my Vagrantfile
successfully (see below). I know it works, because the "print" statement
prints out the value.
When I try to assign that value to one of the node variables, though, the
variable remains empty.
Any ideas?
config.yaml
--
I'm dumb. Using the variable name "config" was an obvious conflict with:
Vagrant.configure("2") do |config|
Changing it to a different name fixed it.
On Tuesday, May 23, 2017 at 8:30:25 PM UTC-4, William Saxton wrote:
>
> So, I've populated a YAML fi
I'm using vagrant to provision some pretty basic VM's and everything is
working with the following network setup:
node.vm.network "private_network", ip: "10.0.1.100"
When I connect to my company VPN, though, I can no longer access the VM via
its IP address.
Is there a different vagrant set
point of view, make it work is doable, but if the VPN
> setup is in that way, my personal suggestion will be try to make the right
> thing and ask them to make a network not routable, etc, so you can work on
> your machine.
>
> Thanks
> Alvaro.
>
> On Fri, Jun 2, 2017 at 7:0
