-
Notifications
You must be signed in to change notification settings - Fork 100
Permission denied #237
Comments
What's your umask? |
~$ umask |
Hrm.... This is definitely a permissions issue between the VM and the host, but I'm not really sure why. |
So the local env is homebrew/rbenv, and I've gotten around chefdk and local gems conflicts by putting /opt/chefdk/bin first in my path, but otherwise nothing springs to mind. |
Recently I updated ChefDK from 0.2 to 0.3.5. and also getting similar error.
|
I see |
My project is here if you'd care to give it a look: https://github.com/pelias/vagrant I'm also using ChefDK 0.3.5 and vagrant-berkshelf 4.0.0. |
the cookbook |
I went ahead an moved some things, namely nesting the actually cookbook under cookbooks/ rather than having it in the top level, and things work now. I gather the contents of .git was being pulled in by berkshelf and the resultant permissions on those files were not as expected. |
Quick workaround in /opt/chefdk/embedded/apps/berkshelf/lib/berkshelf/berksfile.rb, add '.git' in sync exclusion :
|
This is fixed in Berkshelf as of berkshelf/berkshelf#1342 and will be fixed when a new version of Berkshelf + ChefDK are released. |
In case it helps anyone, the above workaround didn't work for me, needed:
|
This is not an edge case. When can we see a new release of Berkshelf + ChefDK? |
@franklinwise unfortunately we have no control over the release cycles of ChefDK. Berkshelf is already out and updated. |
@sethvargo - understand, thanks |
new Chef-DK 0.4.0 is out but this fix isn't included, isn't it? |
It seems to happen when there are git repos in cookbook subfolders. Building on @ericcitaire and @brk3 comments I changed '.git' to '**/.git' in |
Same happens to me after upgrading to chefdk 0.4.0 |
Had the same issue after restarting the computer. The workaround was:
Worth mentioning my I wonder if it has to do with restarting without |
joelhandwell's script referenced above works for me. I'm using chefdk 0.4.0, Vagrant 1.7.2 and vagrant-berkshelf 4.0.3 |
@joaocunha and @quietcat it worked for me as well, thanks! ERROR was about the 'sendmail' community cookbook:
|
Thx for the quick fix. |
+1 for @quietcat 's #237 (comment) working |
I'm a little mystified by this. I'd been using vagrant-berkshelf 2.x for a while without issue. Having upgraded to 4.0.0, I'm in the following situation:
vagrant up
proceeds without issue, however if I halt and then restart the box, or try to reprovision it, I get the following error:If I
rm -rf /Users/grant/.berkshelf/vagrant-berkshelf
, I can run successfully, but again, subsequent attempts will fail.Any idea what's going on? No commands are being run with sudo or as different users, etc. The perms on the files that I get the access error for are 444, owner/group as I'd expect.
... and it would appear that a
chmod -R 755 ~/.berkshelf/vagrant-berkshelf/
resolves the problem.The text was updated successfully, but these errors were encountered: