[vagrant-up] Vagrant 2.2.8

Hi everyone, We are pleased to announce the release of Vagrant 2.2.8. This release includes a number of improvements as well bug fixes. It also includes VirtualBox provider support for the experimental disks feature. Some notable updates in this release include: * Update to Ruby 2.6 *

[vagrant-up] Vagrant 2.2.6

Hi everyone, We are pleased to announce the release of Vagrant 2.2.6. This release includes a number of improvements as well bug fixes. Notable updates included in this release: * Inclusion of Alpine guest support (plugin no longer required) * New before and after options for customized

[vagrant-up] Vagrant 2.2.4

Hi everyone, I'm pleased to announce the release of Vagrant 2.2.4. This release includes a number of improvements as well bug fixes. Notable updates included in this release: * SSH communicator upload fixes for OpenSSH modifications * Added reboot guest capability to Windows * Path import

Re: [vagrant-up] "tls: unknown certificate authority" erros with vagrant-vmware-utility

Hi Will, My apologies for the delay. I've picked up your support ticket so please feel free to respond there. Cheers! - Chris On 2/3/19, Will Froning wrote: > Hello All, > > I've a fresh install of Fedora 29 where vagrant with the vmware-desktop > plugin isn't working. > > System Details: > >

[vagrant-up] [ANN] Vagrant 2.2.3

Hi everyone, I'm pleased to announce the release of Vagrant 2.2.3. This release includes a number of improvements as well bug fixes. Notable updates included in this release: * Added support for Void Linux as host platform * Correct provisioning behavior with the snapshot command * Support for

[vagrant-up] [ANN] Vagrant 2.2.1

Hi everyone, I'm pleased to announce the release of Vagrant 2.2.1. This release includes a number of new features, improvements, and bug fixes. Notable updates included in this release: * Default all network interfaces to virtio in VirtualBox * Support for VirtualBox 6 * Support for ed25519

[vagrant-up] [ANN] Vagrant 2.2.0

Hi everyone, I'm happy to announce the release of Vagrant 2.2.0. This release includes a number of new features, improvements, and bug fixes. Notable features included in this release: * New Vagrant `cloud` command for interacting with Vagrant Cloud * New Vagrant `upload` command for one-off

[vagrant-up] [ANN] Vagrant 2.1.4

Hi everyone, I'm happy to announce the release of Vagrant 2.1.4. This was a patch release following the 2.1.3 release to resolve issues loading some plugins. Many features and improvements are included in the 2.1.4 release: * Project specific plugins * Retention of source box information for

[vagrant-up] [ANN] Vagrant 2.1.0

Hi everyone, I'm happy to announce the release of Vagrant 2.1.0. This release includes a number of improvements, bug fixes, and a new feature. Notable updates include: * Updates to the docker, chef, and puppet provisioners * Disable automatic exception reports by default * Improved Hyper-V

[vagrant-up] [ANN] Vagrant 2.0.4

Hi everyone, I'm happy to announce the release of Vagrant 2.0.4. This release includes a number of improvements, bug fixes, and a new feature. Notable updates include: * Proper file permissions on generated ssh private keys (both POSIX and Windows platforms) * Fix timeout errors on Windows

[vagrant-up] Re: Windows Update Causes Vagrant not to work

Hi there, The problem is that your installation of virtualbox is too old. Upgrading to the latest virtualbox version will fix this problem. Cheers! - Chris On Monday, April 16, 2018 at 4:45:10 AM UTC-7, sam.ziel...@myhealthtest.com wrote: > > I had a Windows Update run a couple of days ago.

[vagrant-up] Vagrant VMware Plugins - Recommended Upgrade

If you have any problems updating to the new Vagrant VMware Desktop plugin, please send an email to supp...@hashicorp.com. Cheers! - Chris Roberts -- This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior

[vagrant-up] [ANN] Vagrant VMware Desktop plugin 1.0.0

The announcement of the plugin release can be found here: https://www.hashicorp.com/blog/introducing-the-vagrant-vmware-desktop-plugin Cheers! - Chris Roberts -- This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html

[vagrant-up] [ANN] Vagrant 2.0.3

Hi everyone, I'm happy to announce the release of Vagrant 2.0.3. This release includes a number of improvements and small bug fixes. Notable updates include: * Support latest update of the Windows Subsystem for Linux * Automatic host remapping for deprecated atlas domain * Host change

[vagrant-up] [ANN] Vagrant 2.0.2

Hi everyone, I'm happy to announce the release of Vagrant 2.0.2. This release includes a number of bug fixes, enhancements, and some new features. Notable updates include: * Updated SMB synced folder implementation * Addition of macOS host support to SMB synced folders * Improved NFS service

[vagrant-up] [ANN] vagrant-vmware-fusion/workstation 4.0.25

log.md#4025 Cheers! - Chris Roberts -- This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list. GitHub Issues: https://github.com/mit

[vagrant-up] Re: Vagrant GitHub Repositories

jeudi 14 septembre 2017 23:51:48 UTC+2, Chris Roberts a écrit : >> >> Hi everyone, >> >> I am happy to announce that the Vagrant code repository has moved under >> the HashiCorp organization on GitHub. The new location of the repository is: >> >> htt

[vagrant-up] Vagrant GitHub Repositories

Hi everyone, I am happy to announce that the Vagrant code repository has moved under the HashiCorp organization on GitHub. The new location of the repository is: https://github.com/hashicorp/vagrant Cheers! - Chris Roberts -- This mailing list is governed under the HashiCorp Community

[vagrant-up] [ANN] Vagrant 2.0.0

release can be found here: https://www.hashicorp.com/blog/hashicorp-vagrant-2-0/ Cheers! - Chris Roberts -- This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your

[vagrant-up] [ANN] Vagrant 1.9.8

Hi everyone, I'm pleased to announce the release of Vagrant 1.9.8. This release includes a number of bug fixes and improvements. The full list of changes can be found in the CHANGELOG: https://github.com/mitchellh/vagrant/blob/v1.9.8/CHANGELOG.md Cheers! - Chris Roberts -- This mailing list

[vagrant-up] [ANN] Vagrant 1.9.7

list of updates can be found in the CHANGELOG: https://github.com/mitchellh/vagrant/blob/v1.9.7/CHANGELOG.md Cheers! - Chris Roberts -- This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those

Re: [vagrant-up] VMWare Fusion Plugin with bundler-executed Vagrant

Hi James! After getting a local setup to match your own I was able to chase down the root cause, bundler. The plugin isn't playing nice when bundler is involved and it re-executes via the sudo helper to interact with vmware. Since the bundle isn't set back up during the re-execution it is unable

[vagrant-up] [ANN] Vagrant Cloud is Moving on June 27th

We are excited to announce that HashiCorp Vagrant features will be extracted from Atlas on June 27th into its own product, HashiCorp Vagrant Cloud. Features include: - *Vagrant Box Creation* to publish public or private Vagrant boxes for

[vagrant-up] [ANN] Vagrant 1.9.5

Subsystem for Linux. The full list of updates can be found in the CHANGELOG: https://github.com/mitchellh/vagrant/blob/v1.9.5/CHANGELOG.md Cheers! - Chris Roberts -- This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html

[vagrant-up] [ANN] Vagrant 1.9.4

/mitchellh/vagrant/blob/v1.9.4/CHANGELOG.md <https://github.com/mitchellh/vagrant/blob/v1.9.3/CHANGELOG.md> Cheers! - Chris Roberts -- This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of

[vagrant-up] Re: VBoxManageControlVM.cpp error

Looks like this might be related to an issue with VirtualBox VMs not being able to resume after the host system has been put to sleep: https://www.virtualbox.org/ticket/15378?cversion=0_hist=1 On Tuesday, February 28, 2017 at 8:21:35 PM UTC-8, Joaquin Menchaca wrote: > > Is this normal? > >

[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

://github.com/mitchellh/vagrant/blob/v1.9.2/CHANGELOG.md Cheers! - Chris Roberts -- This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list

[vagrant-up] Vagrant 1.9.1

Hi everyone, I'm pleased to announce the release of Vagrant 1.9.1. This release includes fixes to Vagrant's internal plugin system. The full list of updates can be found in the CHANGELOG: https://github.com/mitchellh/vagrant/blob/master/CHANGELOG.md#191-december-7-2016 Cheers! - Chris Roberts

Re: [vagrant-up] Unable to SSH to xenial vagrant box

Hi! Uncomment the following line in your Vagrantfile: #config.ssh.insert_key = false and then run: vagrant halt --force vagrant destroy vagrant up If that doesn't work, please let me know. Related GH fix that will be included in the next release:

Re: [vagrant-up] vagrant box add error downloading

Hi! I believe the issue you are running into can be fixed by installing the visual studio c++ redistributable package available here: https://www.microsoft.com/en-us/download/details.aspx?id=8328 If that doesn't fix things up, please run the command again with the --debug flag and provide the

Re: [vagrant-up] ISSUE : Authentication failure. Retrying... after Key inserted!

Hi! First destroy the existing instance: vagrant halt --force vagrant destroy Next, in your Vagrantfile, disable the ssh key insertion: config.ssh.insert_key = false and then run: vagrant up If that doesn't resolve the issue, let me know. Cheers! On Wed, Aug 24, 2016 at 11:56 AM,

Re: [vagrant-up] Node dependency

Hi! > Once I am done with both vms, how can I go I back and configure first VM? The functionality you're describing is not currently implemented within vagrant, however, it is functionality that I intend to implement in the future. Currently vagrant will start and provision instances in order.

Re: [vagrant-up] Vagrant up returns 'rsync could not be found' [debian/jessie64]

For the debian/jessie64 box you tried to up, did you include the ssh config line to disable the key insertion? The applicable line is: config.ssh.insert_key = false If not, include that in the Vagrantfile and re-up the instance. If it still fails, halt the instance and then run: vagrant up

Re: [vagrant-up] Retry failed provisioners

Hi Dan, You are correct that you cannot receive the exit code of a provision task from within the Vagrantfile. Vagrant provisioners do not currently support retries on failure. One option is to re-run a vagrant provision on the failed node, and then vagrant up again. The other would be

Re: [vagrant-up] Provision fails

Hi! It looks like the Vagrantfile is setting up custom facts for host_uid and host_gid using the values previously generated for the nfs setup, and that is causing problems when those IDs don't exist within the VM. It's not clear to me why those are being used as I believe the map_uid and map_gid