-
Notifications
You must be signed in to change notification settings - Fork 4.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Parent folders of synced_folder are owned by root #2257
Comments
For now, my solution is to make the synced_folder directly in the $HOME folder. This is my complete (working) Vagrantfile: https://gist.github.com/nathany/6662802 |
This is working as intended. If you need to change the permissions, use an inline shell provisioner. The permissions you specify on shared folders will only apply to the deepest child. Otherwise, typical umask takes place. |
Care to explain why or offer any advice? Thanks. |
@nathany I ran into the same problem. My solution was to run (I realize I'm replying to a comment almost a year old, but I too expected that setting the owner and group would also apply to the parent folders created) |
For the record: I also think that this is unexpected. I got bitten today, too. |
This is the intended behavior but it is not obvious. When setting up synced folders that require parent folders (e.g. folders that live in Go's `GOPATH`) this has the potential to catch users off guard. See hashicorp#2257.
When I setup a synced folder like so:
The src folder is owned by vagrant:vagrant but the go folder is owned by root:root. This prevents the pkg and bin folders from being created later.
Adding
owner: "vagrant", group: "vagrant"
did not remedy the situation.Vagrant 1.3.3, VirtualBox 4.2.18 r88780, OS X 10.8.5, precise64, inline shell provisioning
The text was updated successfully, but these errors were encountered: