I just ran in to this problem, and while the solution I found certainly won't be for everybody, it was a subtle part of my setup that was causing the issue.
To save space, I'd moved the Docker directory from my %APPDATA% directory on my SSD, to my much larger HDD, and setup a junction to point to it in its new home.
I eventually remembered that this was the ...
Following Gerald Schneider's comment since I already had a Docker swarm ongoing on my three hosts, I have used https://github.com/gongonpower/glusterfs-swarm successfully to set gluster up.
The only change necessary was, for this use case, the create command should be simply
gluster volume create gv0 gfsc1:/bricks/brick1/gv0 gfsc2:/bricks/brick1/gv0 gfsc3:/...
You can't. This isn't something NFS supports. You can only set an SELinux context as a mount option, that will be applied to every file access by the client. None of this has any effect on any SELinux contexts that might exist on the server, and indeed, there might not be any at all.
if you use csf firewall and nfs does not mount you most likely miss the open ports used by nlockmgr, find them by typing
Next edit /etc/sysctl.conf to LOCK the ports on these numbers (example port) and add these 2 lines. Then restart portmap, nfs-server.
There is a nice article on linuxjournal Encrypting NFSv4 with Stunnel TLS which explains how to use stunnel to protect NFSv4 traffic.
Inspired by this publication the NFS IETF working group on RPC-over-TLS protocol, that aims to add a native TLS support to NFS protocol (and any other protocol based on ONC/Sun RPC).