What have you tried?
this post was submitted on 15 Mar 2026
20 points (100.0% liked)
Selfhosted
56953 readers
1548 users here now
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
-
No low-effort posts. This is subjective and will largely be determined by the community member reports.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 2 years ago
MODERATORS
Nothing man, and he's all out of ideas!
There's an official doc about this: https://trapexit.github.io/mergerfs/latest/remote_filesystems/
Have you tried those things?
Sorry, I've missed all the notifications. Thanks a lot, I'll have a look straight away!
I had the same issue with mergerfs + nfs, and fixed by following the official doc here
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.
You need to set the fsid fort your export entry in the NFS server since they are all on the same actual mountpoint.
@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.
I'm not a fan of the kernel NFS server implementation.
I have less headaches when I switched to NFS-Ganesha.