Vagrant up had an error: mount.nfs: access denied by server while mounting 192.168.47.1:/root/workspace/xiujuan/scf/.fissile/.bosh

[xiujuan95]

I fellow the guide of deploying SCF on Vagrant to deploy SCF in my environment. But I met a problem when I ran the command (vagrant up) to set up a virtualbox. Details about the error are shown below:

Vagrant version: Vagrant 2.0.1

In order to solve it, I find a method by Google searching. But I can't check it. Please refer to hashicorp/vagrant#9918 about this method.
I think maybe you can try it. If there has any ideas, please let me know. Thanks

[mook-as]

Do you have multiple network interfaces on your host (what appears to be cf-lite-dev)? I believe @jandubois mentioned something about Vagrant finding the wrong interface (and putting the wrong thing in /etc/exports) in that case.

If that is your issue, it appears that the relevant tickets are hashicorp/vagrant#5424 / hashicorp/vagrant#8704 (and we can't fix it from the SCF side).

[xiujuan95]

Thank you for your ideas. I have fixed it by switching the working directory. Before, I ran "vagrant up" in scf folder. I exit it to run the command and everything is normal. I will close this issue.

[jandubois]

I have fixed it by switching the working directory.

I'm amazed that this works. Vagrant normally starts a VM based on the Vagrantfile in the current directory. If you are switching to a different directory, you are no longer starting the SCF development VM, but some other VM that is described by the Vagrantfile in that directory...

[xiujuan95]

@jandubois You are right. If I want to start the SCF development VM, I must set up a VM in scf folder. Before, I didn't understand it. About this, I'm so sorry! I will refer to the comment of @mook-as to solve this problem again. Besides, if you have any ideas, please let me know. Thanks!

[xiujuan95]

Because the network IP address conflict in our environment. Now, I have fixed this problem. So I will close this issue.

[mickdewald]

If you are coming here because you are using macOS Catalina, this might help: hashicorp/vagrant#10961

TL;DR;
I had to change the link to the mounted directory to the following structure:
/System/Volumes/Data/Users/{user}/{your_project}/

Seems to be a bug in Catalina as far as I understand.

[iamfinky]

So I just resolved this on my Catalina install. After trying all kinds of variations, I renamed my project folder to remove the space in its name and this seems to have fixed the issue.

So it looks like whatever Vagrant is doing to generate /etc/exports doesn't account for " " in the path.