Unusual behavior with macOS and Vagrant with NFS makes me think it’s worth also trying this edit in your Vagrantfile
, replacing this line as follows:
trellis_config.wordpress_sites.each_pair do |name, site|
- config.vm.synced_folder local_site_path(site), nfs_path(name), type: 'nfs'
+ config.vm.synced_folder local_site_path(site), nfs_path(name), type: 'nfs', mount_options: [ 'nolock', 'vers=3', 'tcp', 'fsc', 'rw', 'noatime']
config.bindfs.bind_folder nfs_path(name), remote_site_path(name, site), u: 'vagrant', g: 'www-data', o: 'nonempty'
end
Then apply these changes by running this:
vagrant reload
If that helps, then
- credit goes to @ben
- and weird, because I vaguely thought the issue was resolved as of macOS 10.13.2