Open kenorb opened 8 years ago
@kenorb Could you make it work at the end?
I guess, I had to remove synced_folder line at all, because it seems that /vagrant folder is synced automatically for aws provider. So I'm using synced_folder only for virtualbox provider, but not aws. My Vagrantfile.
This sounds like workaround, until somebody explain what's happening.
Got it. As I thought there will be no straight forward option on making this working. NFS and rsync are only out-of-box options that should work with AWS provider and NFS won't work there. With virtualbox you get vboxfs which is N/A anywhere else.
FYI this issue is a dupe of another much earlier ticket here started by the repo owner as a bounty hunt for making bi-directional sync.
Suggest closing as repo owner is aware already :)
This is follow-up from mitchellh/vagrant/issues/7430
When running Vagrantfile without
config.vm.synced_folder
, somehow my/vagrant
folder is synced with my local folder by default as shown below:but the folder is not synchronized and the changes on one of the site aren't transferred back (the dir doesn't show in
mount
, so probably it was just one time transfer). I'm not sure by which option this is enabled.However I would like to have two-way synchronization, so when I'm activating:
with:
I've got the following error:
My security group allows port 2049 (TCP&UDP) which I hope it's enough. Running debug log as above, doesn't help much.
I'm using Ubuntu 14.04.3 LTS (Trusty Tahr) instance which doesn't have nfsd installed.
Note: I'll install
sudo apt-get -y install nfs-kernel-server
and I'll update the info.