Vagrant tries mounting nfs synced folder with 10.0.2.2

[eden1991]

I'm trying to setup a synced folder with nfs but vagrant tries to mount using 10.0.2.2 instead of 192.168.64.1 and consequently fails:

==> default: Mounting NFS shared folders...
    default: /Users/MYDIR/workspace/imaging/qemu-imaging => /vagrant
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

mount -o vers=3 10.0.2.2:/Users/MYDIR/workspace/imaging/qemu-imaging /vagrant

Stdout from the command:



Stderr from the command:

mount.nfs: an incorrect mount option was specified

Running the mount command by hand with 192.168.64.1 works:

mount -o vers=3 192.168.64.1:/Users/MYDIR/workspace/imaging/qemu-imaging /vagrant

Here is my Vagrantfile:

Vagrant.configure(2) do |config|
    config.vm.box = "custom/rhel96"
    config.vm.box_url = "file://../builds/rhel-9.6-x86_64.box"
    config.ssh.insert_key = false
    config.vm.synced_folder ".", "/vagrant",
      type: "nfs",
      nfs_version: 3,
      nfs_expoer: true,
      nfs_udp: false

    config.vm.provider "utm" do |u|
      u.name = "tfrunner"
      u.cpus = 2
      u.memory = 4096
      u.check_guest_additions = true
    end
  end

Any idea why it tries to use 10.0.2.2? Is there a way to override it with 192.168.64.1?

[naveenrajm7]

Hi @eden1991

10.0.2.2 is the default static reachable IP address from your VM.
I think this IP address works , if your VM has emulated VLAN interface with dhcp enabled.

The 192.168.x.x IP is coming from MacOS and due to the use of shared Interface and it can vary. Since vagrant is unaware of this dynamic IP , they use a static one.

I had similar experience with packer plugin when VM had to reach service running in the host.
Using 192.168.x.x mostly works but it's manually getting that IP.
10.0.2.2 is used for automated operations but only works when you have emulated interface with dhcp enabled.

[eden1991]

I wasn't able to figure this out unfortunately. Network tests were successful i.e. nc -zv 10.0.2.2 2049, but things like rpcinfo -u 10.0.2.2 nfs & showmount -e 10.0.2.2 were still failing. Must be something on my machine blocking it..

However SMB mounting seems to do the trick!