Closed tuminoid closed 10 years ago
That sucks =/ I wasn't able to upgrade to 1.4 yet, but I don't see why we'd have a problem on the plugin as we just use a synced_folder
under the hood.
Since that relies on some ugly monkey patching, I'm not sure if something has changed on vagrant core that would make it no longer work.
@tuminoid would you mind trying to use a regular NFS synced folder to check if vagrant picks it up and if it works fine?
@fgrehm Yes, it picks up NFS synced folder normally.
Ok, thanks for reporting.
I'm tagging it as a bug and will get to it once I'm able to upgrade to 1.4 (hopefully by next week). If someone else has made the upgrade and wants to jump in, feel free to do so!
Just came to report this and found an issue already in place. Always nice to have company in bugs! :bug: :grinning:
If I get the chance I'll try to dig in and take a look. It seems like getting out of monkeypatch-ville is really going to be the key here, since it seems like we're missing a hook on the newer code. :monkey_face:
Yeah, unless a new feature comes in time for the next release I'm 100% up for getting rid of the monkey patch once and for all and drop compatibility for Vagrant < 1.4 :smiley:
This was fixed by GH-73 and is available from the 0.5.1 version of the plugin :-)
Running Mac OS X 10.9 and VMWare 6.0.2 with vagrant-vmware-fusion plugin.
Today I upgraded to Vagrant 1.4.0. I reinstalled vagrant-cachier via uninstall/install as per request. I have completely destoyed VM and its
.vagrant
directory.I have
~/.vagrant.d/Vagrantfile
withand upon booting VM, I get:
/etc/exports
on host is and stays empty. Cache is not mounted over NFS and installation explodes thanks to the corrupted packages bug (as expected without NFS).