What have you tried?

There's an official doc about this: https://trapexit.github.io/mergerfs/latest/remote_filesystems/

Have you tried those things?

@remindme@mstdn.social 2 days

I don’t have a good answer but I’m super curious about this.

You say the mount is still fine from the VM, so it must be something with how the docker mounts are configured.

In the early days of docker there used to be a tool that used rsync to sync changes between host and container filesystems when such support wasn’t yet available on some systems (like Mac). I’m wondering if something similar is needed here. Or some additional options in your docker mount mappings.

You need to set the fsid fort your export entry in the NFS server since they are all on the same actual mountpoint.

I have found docker hates locally mounted NFS mounts direct to volume mounts. its kind of like symlinking a symlink of a symlink.

best way I have found that this works is to use CIFS and declare a NAS share to an actual docker volume and then mount that inside the container like any other volume.

personally I would have preferred NFS, but here we are.

it has something to do with how NFS connectivity maintains a connection. it's not "always on" but is inefficient when it quickly needs to reconnect for a read/write request. or at least something like that.

I'm not a fan of the kernel NFS server implementation.

I have less headaches when I switched to NFS-Ganesha.