NFS mount fails with boot2docker v18.09.0

[tonivdv]

With latest release of toolbox, and more specifically boot2docker (v18.09.0) which comes now with Tiny Core Linux, the NFS mount does not work.

[jukra]

Had the same issue, fixed temporarily by forcing docker-machine create to use older boot2docker version.

[tonivdv]

I finally was able to get a new machine up and running with latest boot2docker version and I didn't had any issues setting up ssh ... So not sure there is an issue ... Anyone else can confirm it works?

[coolmic]

Same issue, tried to manually mount from the machine, got this error :

sudo mount -t nfs -o noacl,async 192.168.100.1:/private/var/www/project /private/var/www/project

mount.nfs an incorrect mount option was specified

I tried everything, even sudo mount 192.168.100.1:/private/var/www/project /private/var/www/project Still the same error.

So I downloaded a old version of boot2docker ( like https://github.com/boot2docker/boot2docker/releases/tag/v18.01.0-ce ).

Executed export VIRTUALBOX_BOOT2DOCKER_URL=file://$HOME/Downloads/boot2docker.iso

before creating new machine, and it works now.

[nlfiedler]

Yep, doesn't work, even without mount options. Still okay with Boot2Docker 18.06.1, by the way. Should a bug/question be filed against boot2docker?

[kvokka]

Can someone, please say, will be required removal of all containers for rollback to 18.06.01 from 18.09?

Thank you!

[paolomainardi]

It seems that we've found the issue, a PR is coming.

[mgdesign]

On Mac Osx Mojave (10.14.1) we solved by specifying the nfs server version in the mount command

sudo mount -t nfs -o noacl,async,nfsvers=3 192.168.99.1:/Users /Users

[tonivdv]

Just released a new version 0.5.2 with the fix. Hopefully this solves the new boot2docker issue ;) Thanks again to @paolomainardi's PR

[paolomainardi]

thanks a lot @tonivdv for the quick reaction!

[nlfiedler]

Terrific, thank you.