VVV: vagrant up fails `initialize': Permission denied

I keep getting some sort of permission denied error, apparently related to Ruby:

==> default: Running cleanup tasks for 'shell' provisioner...
/Applications/Vagrant/embedded/gems/gems/vagrant-1.6.2/lib/vagrant/environment.rb:410:in `initialize': Permission denied - /Users/colin/.vagrant.d/data/lock.fpcollision.lock (Errno::EACCES)

It’s completely torpedoed my efforts to get grunt running. I already tried

sudo chmod -R 755 /Applications/Vagrant

Made no difference…

Help!?

About this issue

Original URL
State: closed
Created 10 years ago
Comments: 29 (4 by maintainers)

Most upvoted comments

Had the same problem with the latest version of Vagrant:

opt/vagrant/embedded/gems/gems/vagrant-1.7.2/lib/vagrant/environment.rb:492:in `initialize’: Permission denied - /Users/svenhaveman/.vagrant.d/data/lock.fpcollision.lock (Errno::EACCES)

I fixed this by changing the ownership of the file: chown svenhaveman:staff ~/.vagrant.d/data/lock.fpcollision.lock

Don’t sudo anything, this will lead to other errors.

svenhaveman on Feb 20, 2015

Don’t do the sudo trick on your Mac or Linux build. Something’s permissions are probably off. Do a find . -user root from inside your VVV dir and see if anything is off.

On Wed, Jan 14, 2015 at 2:41 PM, Anton Iliyn notifications@github.com wrote:

vagrant 1.7.2 - same issue

Reply to this email directly or view it on GitHub https://github.com/Varying-Vagrant-Vagrants/VVV/issues/362#issuecomment-69977895 .

-Doug

zamoose on Jan 14, 2015

sudo chmod -R /home/user_name/.vagrant.d

it helps for me

brud on Jan 14, 2015

I have the same issue, this did the trick for me: sudo vagrant up

f0ns on Jan 14, 2015

I just reinstalled my entire operating system. Hopefully that’ll fix it.

UPDATE: Upon further investigation my problems were not anything to do with VVV, it was Vagrant 1.6.x it’s not really stable yet. It doesn’t properly support vagrant-hostsupdater or any other plugin that relies on nokogiri.

For more: https://github.com/cogitatio/vagrant-hostsupdater/issues/28 https://github.com/mitchellh/vagrant/issues/3769

metaColin on May 22, 2014

I had this issue by running sudo vagrant up on Mac and afterwards trying to run it without sudo (which, of course is the preferred way). Simply rm -rf .vagrant* did the trick for me without any negative consequences.

yourkin on May 25, 2019