FlipEverything
commented
7 years ago I can confirm this issue. The mentioned fix works for me too. I removed the line mount_options: ['dmode=775', 'fmode=774'] from the Vagrantfile-local (line 219).
The error message during vagrant up (fresh start):
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!
mount | grep " /mnt/vagrant-mounts/33-33 "
if test $? -ne 0; then
mkdir -p '/mnt/vagrant-mounts/33-33'
chmod 700 '/mnt/vagrant-mounts'
vmhgfs-fuse -o allow_other,default_permissions,uid=33,gid=33,dmode=775,fmode=774 .host:/ '/mnt/vagrant-mounts/33-33'
fi
Stdout from the command:
Stderr from the command:
fuse: unknown option `dmode=775'config.yaml:
vagrantfile:
target: local
vm:
provider:
local:
box: puphpet/ubuntu1604-x64
box_url: puphpet/ubuntu1604-x64
box_version: '0'
chosen_virtualizer: vmware_workstation
virtualizers:
virtualbox:
modifyvm:
natdnshostresolver1: false
showgui: 0
vmware:
numvcpus: 1
parallels:
linked_clone: 0
check_guest_tools: 0
update_guest_tools: 0
...
synced_folder:
vflsf_btaayqt69yr5:
source: 'D:/dev/web'
target: /var/www
sync_type: default
smb:
smb_host: ''
smb_username: ''
smb_password: ''
mount_options:
dir_mode: '0775'
file_mode: '0664'
rsync:
auto: 'true'
owner: www-data
group: www-data
...Windows 10 x64 vagrant 1.8.6 vagrant-vmware-workstation 4.0.14 VMware Workstation 12.1.1
This line in the vagrant file:
mount_options: ['dmode=775', 'fmode=774']causes the new vmware-fusehgfs module to fail. Simply removing it appears to work.