docker-machine-nfs: Verify NFS mount fails

In the newest version (as of today, though ) using the 1.9.0a packages I’m getting a verifying NFS mount error on first run through. Though it works on the second invocation.

Here’s the output of docker-machine-nfs default: [INFO] machine presence … OK [INFO] machine running … OK [INFO] Lookup mandatory properties … OK

- Machine IP: 192.168.99.100
- Network ID: vboxnet1
- NFSHost IP: 192.168.99.1

[INFO] Configure NFS …

!!! Sudo will be necessary for editing /etc/exports !!! Password: OK [INFO] Configure Docker Machine … OK [INFO] Restart Docker Machine … OK [INFO] Verify NFS mount … FAIL

Cannot detect the NFS mount 😦

About this issue

  • Original URL
  • State: closed
  • Created 9 years ago
  • Comments: 39 (8 by maintainers)

Most upvoted comments

I also had this issue and the reason was “Block incoming connections” for nfsd in Preferences -> Security & Privacy" -> Firewall -> Firewall Options.... I have also unchecked option “Automatically allow signed software to receive incoming connections” there and I think that because of that OS X automatically blocks incoming connections for all software by setting “Block incoming connections”, even signed. So you need to manually select “Allow incoming connections” for each blocked software.

Possible workaround:

I try open new terminal session and see message:

Error running connection boilerplate: Error checking and/or regenerating the certs: There was an error validating certificates for host "192.168.99.100:2376": dial tcp 192.168.99.100:2376: i/o timeout
You can attempt to regenerate them using 'docker-machine regenerate-certs name'.
Be advised that this will trigger a Docker daemon restart which will stop running containers.
  1. docker-machine regenerate-certs dev
  2. docker-machine-nfs dev

Nice mounted! 🔮 d632e508f7

I ran into this issue today =/ $ docker -v Docker version 18.02.0-ce, build fc4de44

$ docker-machine -v docker-machine version 0.13.0, build 9ba6da9

€dit: I was able to get it running. The /etc/hosts file on the host machine was missing 127.0.0.1 localhosts Deeplink to solution was: https://github.com/adlogix/docker-machine-nfs/issues/27#issuecomment-167681482