[vagrant-up] Re: NodeJS installation problem (via Curl)

Would suggest using DNS from your regular network, and if you don't have one, make one using root hints. What I do at my place, that way don't get ISP filtered content. -- This mailing list is governed under the HashiCorp Community Guidelines -

Re: [vagrant-up] [ANN] vagrant-vmware-fusion/workstation 4.0.17

Hi Chris, just wondering: wasn't linked clones already supported for VMware Workstation already ever since Vagrant 1.8 came out? Or is there anything new to this? Cheers, Torben Am 28.02.2017 6:25 nachm. schrieb "Chris Roberts" : > Hi everyone, > > I'm pleased to

[vagrant-up] Re: Vagrant 1.9.2 download not available

Hey Ernesto, There was a slight delay on the packaging side. They are available now for download. Cheers! - Chris On Tuesday, February 28, 2017 at 7:41:36 AM UTC-8, Ernesto Iser wrote: > > Hi, I was wondering when the 1.9.2 version of vagrant will be available > for download, the website is

[vagrant-up] [ANN] Vagrant 1.9.2

Hi everyone, I'm pleased to announce the release of Vagrant 1.9.2. This release includes support for packaging Hyper-V boxes, updates to the WinRM communicator, and a collection of bug fixes to Vagrant core and guest plugins. The full list of updates can be found in the CHANGELOG:

[vagrant-up] Vagrant 1.9.2 download not available

Hi, I was wondering when the 1.9.2 version of vagrant will be available for download, the website is still listing 1.9.1 as the latest version, thanks -- This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in

[vagrant-up] Re: NodeJS installation problem (via Curl)

I found the cause of the problem File "/etc/resolv.conf" on Vagrant contains this "nameserver 10.0.2.3". I just added "nameserver 8.8.8.8" to the first line and it worked! понедельник, 27 февраля 2017 г., 15:28:38 UTC+2 пользователь Dmitriy Ermola написал: > > I have running Vagrant machine