Closed tuminoid closed 10 years ago
Pinging also @phinze as he's in the NFS SWAT team. I'm not especially familiar with the NFS code.
Hi @tuminoid, when you can reproduce the error are you using a stock Vagrantfile
from vagrant init
?
Let me know and I can try to repro on my side.
Yes. I mentioned that in OP (vagrant init precise64
+ vagrant up
).
In ~/.vagrant.d/Vagrantfile
I have the standard cachier config:
config.cache.enable_nfs = true
config.cache.auto_detect = true
config.cache.scope = :machine
and it blows up.
Folks, I just got back from vacations and my next focus will be on getting vagrant-cachier back into shape. I'll try to have a look at this over the week :-)
Originally filed at Vagrant itself https://github.com/mitchellh/vagrant/issues/2748 , but closed as plugin issue, so recreating it here.
Using Vagrant 1.4.2 on MacOSX and having vagrant-cachier enabled with NFS and launching a default precise64 Virtualbox VM gives me this:
Debug log at https://gist.github.com/tuminoid/8234672
It works if in addition to cachier settings you have both
but either alone isn't enough to fix it.
/cc @fgrehm @tmatilai @mitchellh