msg: chown failed when vagrant up

[austinpray]

vagrant destroy -f && vagrant up

My branch: https://github.com/austinpray/bedrock-ansible/tree/H5BPserverconfigs

TASK: [wordpress-sites | Create web root of sites] **************************** 
failed: [default] => (item={'site_install': True, 'admin_user': 'admin', 'site_name': 'example.dev', 'system_cron': True, 'multisite': {'enabled': False}, 'site_title': 'Example Site', 'user': 'vagrant', 'env': {'db_name': 'example_dev', 'wp_env': 'development', 'db_user': 'example_dbuser', 'db_password': 'example_dbpassword', 'wp_home': 'http://example.dev', 'wp_siteurl': 'http://example.dev/wp'}, 'site_hosts': ['example.dev', '192.168.50.5'], 'group': 'www-data', 'admin_email': 'admin@example.dev', 'admin_password': 'admin'}) => {"failed": true, "gid": 20, "group": "dialout", "item": {"admin_email": "admin@example.dev", "admin_password": "admin", "admin_user": "admin", "env": {"db_name": "example_dev", "db_password": "example_dbpassword", "db_user": "example_dbuser", "wp_env": "development", "wp_home": "http://example.dev", "wp_siteurl": "http://example.dev/wp"}, "group": "www-data", "multisite": {"enabled": false}, "site_hosts": ["example.dev", "192.168.50.5"], "site_install": true, "site_name": "example.dev", "site_title": "Example Site", "system_cron": true, "user": "vagrant"}, "mode": "0755", "owner": "501", "path": "/srv/www/example.dev/current/web", "size": 170, "state": "directory", "uid": 501}
msg: chown failed

example.dev is a straight up clone of the bedrock master. Everything was working before I pulled the master and did the NFS upgrade.

this issue blocks: #37

[austinpray]

Weird.

vagrant@example:/srv/www$ ls -l
total 4
drwxr-xr-x 3 root root 4096 Oct  3 02:50 example.dev

vagrant@example:/srv/www/example.dev$ ls -l
total 4
drwxr-xr-x 19 501 dialout 646 Oct  3 02:49 current

vagrant@example:/srv/www/example.dev/current$ ls -l
total 76
-rw-r--r-- 1 501 dialout   380 Oct  3 02:49 Capfile
-rw-r--r-- 1 501 dialout  1173 Oct  3 02:49 CHANGELOG.md
-rw-r--r-- 1 501 dialout  1868 Oct  3 02:49 composer.json
-rw-r--r-- 1 501 dialout  6921 Oct  3 02:49 composer.lock
drwxr-xr-x 6 501 dialout   204 Oct  3 02:49 config
-rw-r--r-- 1 501 dialout  3978 Oct  3 02:49 CONTRIBUTING.md
-rw-r--r-- 1 501 dialout    86 Oct  3 02:49 Gemfile
-rw-r--r-- 1 501 dialout   471 Oct  3 02:49 Gemfile.lock
-rw-r--r-- 1 501 dialout  1044 Oct  3 02:49 LICENSE.md
-rw-r--r-- 1 501 dialout 17506 Oct  3 02:49 README.md
drwxr-xr-x 3 501 dialout   102 Oct  3 02:49 scripts
drwxr-xr-x 3 501 dialout   102 Oct  3 02:49 vendor
drwxr-xr-x 5 501 dialout   170 Oct  3 02:49 web
-rw-r--r-- 1 501 dialout    13 Oct  3 02:49 wp-cli.yml

what's up with dialout?

[austinpray]

Good discussion here: https://coderwall.com/p/uaohzg

[austinpray]

we might have to use this: https://github.com/gael-ian/vagrant-bindfs

[swalkinshaw]

I was having the same issue and this got me past it:

  config.vm.synced_folder '../bedrock', '/srv/www/example.dev/current', type: :nfs, linux__nfs_options: %q(no_subtree_check all_squash rw), map_uid: 0, map_gid: 0

[swalkinshaw]

Looks like linux__nfs_options is just the default so shouldn't need that part.

https://github.com/mitchellh/vagrant/blob/efd1d5e11bfc5a72c7a1d1eae294b4751d841544/plugins/hosts/linux/cap/nfs.rb#L102-L104

[austinpray]

Yeah for some reason that worked

[austinpray]

#72

[030]

@swalkinshaw Thank you. It is possible to execute chown now in the box. The problem we have now is that the user that runs vagrant is not set, but appstore. How could the be solved for all users?