0

I'm running Ubuntu 12.04 with vboxheadless 4.2.10 and vagrant 1.2.7 to provision instances on a server.

When I run vagrant up I get the following errors:

err: /Stage[main]//File[/var/www/example.drupal.dev]/owner: change from 110 to vagrant failed: Failed to set owner to '1000': Operation not permitted - /var/www/example.drupal.dev
err: /Stage[main]//File[/var/www/example.drupal.dev]/group: change from 119 to vagrant failed: Failed to set group to '1000': Operation not permitted - /var/www/example.drupal.dev

Here is the offending puppet conf:

file { "/var/www/example.drupal.dev":
  ensure => "directory",
  owner => "vagrant",
  group => "vagrant"
}

It's mounting through NFS.

The rest of the box provisions fine but this is causing issues when I run my tests. I don't see these issues on OSX or Windows but see it on Ubuntu 12.04. This post (Vagrant OS X host nfs share permissions error - Failed to set owner to '1000') references no_root_squash but you can't apply that because the exports are regenerated on box reload.

I'm unsure how to fix this so would appreciate any help.

3
  • 1
    What kind of filesystem is /var/www/example.drupal.dev on? What happens when you manually try to change the ownership using chown? If this is coming from NFS, then why aren't you changing things on the NFS server?
    – Zoredache
    Sep 12, 2013 at 16:26
  • It's an NFS link between ext4 and ext4 on the guest box.
    – digital
    Sep 12, 2013 at 16:38
  • Same exact issue. Did you have any luck?
    – Jimmy Kane
    Nov 8, 2013 at 18:29

1 Answer 1

1

You must set no_root_squash flag to allow ownership change. See answers here: Vagrant OS X host nfs share permissions error - Failed to set owner to '1000'

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .