Re: [vagrant-up] 'The following settings shouldn't exist: ruby' from pre-up trigger

On Thursday, October 18, 2018 at 1:17:49 PM UTC-7, Brian Cain wrote: > > On Thu, Oct 18, 2018 at 11:03 AM Darren S. > wrote: > >> So it did, thanks! I should have checked that first. >> >> Now that the pre-up trigger is running, I'm noticing that the action I'm >> trying to take (setting

[vagrant-up] Backup strategy for minimal Vagrant backup

I want to back up the minimal files to be able to recreate my Vagrant boxes. Assuming that I have automated the provisioning of each box, is it safe to exclude the .vagrant.d directory? I am also excluding the 'VirtualBox VMs' directory. My assumption is that everything can be re-created after

[vagrant-up] After upgrading virtualbox package, unable to 'vagrant up'

My colleague and I have been using Vagrant for several months to run several VirtualBox VMs on a FreeBSD-11 host. Earlier this month, I ran 'sudo pkg upgrade' on the host. Without specifically intending to upgrade our VirtualBox installation, I upgraded that package. In the course of that

Re: [vagrant-up] Stderr: VBoxManage

try the following open virtualbox gui shutdown/stop the VM try to turn on the VM any error message there ? screenshots welcome On Thu, Oct 18, 2018 at 9:06 PM wrote: > I'm currently running vargant version 2.1.5 on my mac high sierra 10.13.6 > > So after completing the vagrant init and