When using plex in Docker, you want the ability to move the container between hosts (during host maintenance for example).
To achieve this, the plex Metadata (Library root folder) is often mapped to a network storage using docker bind.
In my case the Metadata is stored on a NFSv4.1 share on a NAS device.
However this creates issues with Database files (subfolder Plug-in Support/Databases) not handling network storage well due to locking mechanism (although NFSv4 does have a locking mechanism).
There are multiple posts in the forum about this problem, search for NFS.
My current data sizing is:
- Complete Library Folder : 38 GB
- Database subfolder : 160 MB
Since the issue of network file locking only affects the Database files, it would be helpfull if we could split the folders.
I would like to keep the Metadata on the NFS share (NAS Storage - 38 GB) and only move the Database folder to the local node running the Plex container, or eventually to an iSCSI storage.
Since the Databsae folder is a sub folder of the Metadata structure (Library folder), it is not possible to achieve this just by tweaking the docker binds (or at elast I could not figure it out).
Would it be possible to add another mapping spcific to the Database folder in the Plex docker container (for example /DB) in addition to the exisiting Metadata mapping (/config) ?
This would allow to separate both and use the most suited storage option for both types of data.
