That's actually one of the first things I've tried, It's already inside my home folder. Still no joy.
On Tuesday, October 28, 2014 6:03:29 PM UTC-3, Umair Chagani wrote: > > You should change where vagrant creates VMs to a place where you have full > access. Try setting the VAGRANT_VMWARE_CLONE_DIRECTORY env variable. See > the link below for more details: > > https://docs.vagrantup.com/v2/vmware/configuration.html > > > > > > On Tue, Oct 28, 2014 at 4:59 PM, Hermano Cabral < > [email protected] <javascript:>> wrote: > >> Howdy, >> >> I'm constantly having to take ownership of the .vagrant folder before >> starting up a VM with vmware fusion. If I don't do that, VMWare fusion says >> it cant open the .vmdk due to insufficient permission. >> >> Does anyone know how to fix this? >> >> Cheers. >> >> PS. reinstalling both vagrant and VMWare fusion didn't help. >> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Vagrant" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> For more options, visit https://groups.google.com/d/optout. >> > > -- You received this message because you are subscribed to the Google Groups "Vagrant" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
