I have two Unraid servers (2 licenses). Both are running on different networks. I am wondering whether I can have docker containers access each other? This would require me to mount the array from unraid server #1 as disks on unraid server #2. Would this be possible? Maybe through UD?

On 12/19/2025 at 8:42 PM, steve1977 said:

I have two Unraid servers (2 licenses). Both are running on different networks. I am wondering whether I can have docker containers access each other? This would require me to mount the array from unraid server #1 as disks on unraid server #2. Would this be possible? Maybe through UD?

Correct via Unassigned disk.

you would setup a share via NFS. and then connect to nfs via UD plugin to have a /mnt/remotes/Hostname_Sharename

I have a media server plex instance and other as a separate unraid bare metal instance.

the plex unraid system shares its docker folder:

In my other unraid system Via UD in my unraid VM test instance...



and now my OMV unraid instance can interact with teh docker folder...

This said I recommend using FCP (Fix Common Problems) plugin) as you will need to set access edits if interacting with a remote share via another unraid docker.

FCP will war go over and help you correct proper remote access and interaction with docker and remote connections.

On 12/23/2025 at 10:37 AM, bmartino1 said:

Correct via Unassigned disk.

you would setup a share via NFS. and then connect to nfs via UD plugin to have a /mnt/remotes/Hostname_Sharename

I have a media server plex instance and other as a separate unraid bare metal instance.

the plex unraid system shares its docker folder:

In my other unraid system Via UD in my unraid VM test instance...



and now my OMV unraid instance can interact with teh docker folder...

This said I recommend using FCP (Fix Common Problems) plugin) as you will need to set access edits if interacting with a remote share via another unraid docker.

FCP will war go over and help you correct proper remote access and interaction with docker and remote connections.

This was not exactly what I was looking for, but also seems very interesting.

Are you saying you’re sharing the docker config directories across two unraid servers? One only has read access to avoid data corruption? How does it work with “watched flags”?

Essentially I'm running two of the same docker. And I lm using 1 unraid to run samba shares to be able to go to 1 up to access the content.

1 unraid (non samba) is running, ars stack, Plex, PBS back a ZFS raid z1 of media content.

The only share is my "appdarafolder" a Docker folder that contains data for a docker makemkv. As this system is a bit remote. (Tail scale access)

And the docker folder for make MKV so I can rip my own media local at home or in that machine when on site...

This way if I'm home and have a disk make MKV can still throw my media to the correct system (via nfs) on my samba unRAID system...

Usually when you want 2 unRAID systems to talk with each other you use NFS.

Thanks for detailed write-up. I am but confused though.

You say that you suggest NFS shares, but you use SMB shares yourself? Why is this?

Let me try to recap your setup

Unraid Server #1 (home)

• Appdata with arr dockers, Plex docker [unshared]

• Appdata with makemkv docker [shared]

• ZFS pool for media

Unraid Server #2 (remote)

• Appdata with makemkv docker [using mapped appdata from unraid server #1, only read access]

nfs for liunx only smb for apple / windows.

I run NFS for UNRIAD to UNRaid only.

SMB is for any other client that connects to my system.

Apologies if that is not clear.

let me try to re-explain my setup... if only to clear confusion and go over my refactor a bit... as I'm testing some things what if and i can therefore i will, but doesn't mean its stable nor one should copy what I'm doing...

I was trying to inform and give you the correct method for unriad to unriad.

In truth you can use webdav, sftp, smb(samba) nfs any network system via network to share connected between 2 systems. unraid ships with nfs and samba. and for linux to liunx communication, its best to use nfs. This is due to rules and being able to share the folder to a select ip or ip range and be secure while maintaining file integrity, permission and other options...

So I have Remote system:
Main job, Plex. I have dockers I want accessible.

I can go to 192.168.x.x and see my system



NFS is being wonky (as I have done similar test with v7 beat and RC candidates..) aside, so I recent changed it back to public:*the share would be secure/private and a nfs exports rule would be set....

*as you can see the plex unraid is using this folder share via nfs in public mode...

unraid setting requires nfs enabled for both the server and the UD system to connect...

you can edit the default unraid appdata settings. as mentiond before to share your docker data. If you stay with unraid defaults.

in my case this is ZFS. i have a dataset called Dockers


My goal:
I want to still rip disk remotely and have them plex accessible. or be local when on site and still be able to rip disks on unraid plex...

so I nfs share this folder for my main samba system my master browser. so i only have to go to 1 ip address for all my necessary data

My home machine in a VM:

Thus my home unraid instance...

I use unassigned disk and mount my nfs share to be able to talk see and write files



* I actual use a user scirpt. As I was testing nfs, 9p9mode and virtfs with vms... Decided after i got it working to why have another point of failure if proxmox connects first then passes so I moved the nfs connection into my main OMV unraid instance.

I run quite a bit of custom workaround code... (one thing leads to another. but I know my way around the system...)

Normally one would set up and use UD with automount..

*in my case this borked some things and I wanted teh mount else where...
--Again recently finshed testing to do nfs edtis and check pve vm stuff with unraid...

so Instead In my smb edits.... for my one host all systems connection. (as i have data on pve, I have doat on pelve unraid... and I have data on OMV... I want 1 sytem to go to for samba and the doata there within...

so in my netowrk a system would go though
Client > OMV > NFS > plex folder

Client > OMV > Samba> PVE ZFS folder

I run the mount command that UD does and rebind it to /nfs ... as I orginal mounted nfs via pve and into the VM by another virtfs.... so my previous data fo mount points for PVE OMV... as Unriad is only geting a qemu Vdisk for dat... PVE is my zfs data pool and control system. But all my data from ZFS is on my PVE instance so SMB mount and others...

*Original was going to use remotes, but nfs pve to unraid and didn't like what the UD makes as it generates treible name paths... UD mounts these at "/mnt/remotes" and that is not easy to type and use when in testing... so for quick writes as I have issues with keybaords and buttons :/ to help with quick writes where I can now use "/nfs" when refering to my plex stuff on another system...

so I took control and ran a workaround to make it do What I want it to do and How I want to interact with it...

so now I can interact with /nfs as if I was on the Plex OMV server, but I'm on my OMV instance using NFS.

POSIX, permission and other tom fooly aside. this is the known and correct way for linux to handle and use file sharing between other linux ssytems.

so what about the docker! so now my docker needs sahred mount spaces
OMV:

I can mount map and set this to use the nfs share path /nfs. FCP checks and fixes these things (atleast warns that hey you should do this because this...) as I'm using a remote folder for a docker and due to unraid "Fuse" for making and mount things at /mnt/user ... I need to set a "slave" read/write in the docker settings in the event of network failure nd the nfs connection is down where OMV can't talk to my plex unraid instance...



And this is why I said what I said and why i'm doing what i'm doing in this current refactor.

this allows me to use the same docker at home or remote to interact with 2 separate systems. Bare-metal and VM betwwen 2 unraid instances and dockers.