Vagrant: Permission denied @ dir_initialize

Created on 2 Aug 2019  ยท  14Comments  ยท  Source: hashicorp/vagrant

I've been wrestling with this issue for a few hours. I cannot execute the vagrant command at all.

Vagrant version

2.2.5

Host operating system

Mac OSX 10.12.6

Guest operating system

N/A

Vagrantfile

N/A, cannot even run vagrant command

Debug output

https://gist.github.com/mattkoch614/3a4251dcd2100b7abba69096ba0ca623

Expected behavior

vagrant command runs successfully

Actual behavior

Error. See Debug output

Steps to reproduce

  1. Install Vagrant 2.2.5
  2. Install VirtualBox 6.0
  3. Open Terminal
  4. Run vagrant command
needs-debug-gist waiting-reply

Most helpful comment

Yeah, tell me about it! This has been driving me crazy for a while. I was hoping it was something basic like this. After running the following:

sudo chmod 755 /Users

This sorted itself out. Thank you for walking through things with me!

All 14 comments

Hi @mattkoch614 - Do you have the full debug log for running vagrant?

@briancain - Sorry, forgot the debug flag for my output. The gist has been updated.

Does the user that is invoking vagrant have permission to read the /Users dir on your filesystem? It seems like that dir might be locked out of whatever user you are using to run vagrant with.

I am the user invoking the command, and that user has access to /Users/(my username). I fear that something may have gotten tangled up by running sudo vagrant up at one point, causing issues with permissions, but I cannot figure out how to get going again.

Ahh, yes, That is for sure what happened. What are the permissions for your folder at ~/.vagrant.d? I'm guessing it's probably locked out from running sudo.

total 16
drwxr-xr-x  2 kochm  DOMAIN\Domain Users    68 Aug  2 11:51 boxes
drwxr-xr-x  4 kochm  DOMAIN\Domain Users   136 Aug  2 13:22 data
drwxr-xr-x  4 kochm  DOMAIN\Domain Users   136 Aug  2 13:22 gems
-rw-------  1 kochm  DOMAIN\Domain Users  1675 Aug  2 11:51 insecure_private_key
drwxr-xr-x  3 kochm  DOMAIN\Domain Users   102 Aug  2 11:51 rgloader
-rw-r--r--  1 kochm  DOMAIN\Domain Users     3 Aug  2 11:51 setup_version
drwxr-xr-x  2 kochm  DOMAIN\Domain Users    68 Aug  2 11:51 tmp

It would be the actual directories permissions rather than the content inside it. I'm guessing it's probably owned my root, or only readable/writable by root.

Here we are:

drwxr-xr-x  10 kochm  DOMAIN\Domain Users     340 Aug  2 13:22 .vagrant.d

That's the current permission set of the .vagrant.d folder. I'm at a loss as to what needs to happen at this point - I was able to use Vagrant just fine in the past. This time, I reinstalled both Vagrant and VirtualBox completely to see if that would help, but no dice.

And what about your /Users directory?

That one is owned by root.

d-wx--x--x    6 root  admin    204 Feb 13  2018 Users

Ah ok, that's the problem it looks like. Whatever happened, your Users folder now doesn't have read permissions set. If you fix that (and there are no other permissions issues) then Vagrant should work. I imagine some other tools might be broke for your local user too with those permissions :sweat_smile:

It's fine that they are owned by the root/admin user/groups but the permissions looks wrong to me. I don't know what the default permissions are for macOS, but for example, my home dir on linux has these permissions:

brian@localghost:vagrant-sandbox % l / | grep home                                                                                                  ยฑ[master]
drwxr-xr-x   3 root root 4.0K Sep 27  2018 home

Yeah, tell me about it! This has been driving me crazy for a while. I was hoping it was something basic like this. After running the following:

sudo chmod 755 /Users

This sorted itself out. Thank you for walking through things with me!

I'm going to lock this issue because it has been closed for _30 days_ โณ. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

RobertSwirsky picture RobertSwirsky  ยท  3Comments

janw-me picture janw-me  ยท  3Comments

StefanScherer picture StefanScherer  ยท  3Comments

DreadPirateShawn picture DreadPirateShawn  ยท  3Comments

tomhking picture tomhking  ยท  3Comments