Creating shared folders and other folders in OMV, Docker and Portainer

For linuxserver/plex you don't need a transcode folder anymore.

From https://hub.docker.com/r/linuxserver/plex

Zitat

04.12.19: - Add variable for setting PLEX_CLAIM. Remove /transcode volume mapping as it is now set via plex gui and defaults to a location under /config.

Otherwise you should be good.

Suggest to use the docker-compose from here in Portainer.

After almost three years with OMV I have recently come to take up a minimalist approach to shared folders. I started out making every media folder - movies, photos, tv, etc., etc. a shared folder, and then mapping each one in my Plex yml. Now I only include one volume path for media and set up the folders from within Plex. Like this:

volumes:
  -/srv/dev-disk-by……/media:/media
  -/srv/dev-disk-by……/appdata/plex:/config

My main server only has four shared folders: appdata, data, media, and nextcloud. You could easily have just two shared folders: appdata and data. Appdata can contain all your containers’ config folders, and the data folder can contain all the “media” folders, documents, downloads, etc.

The takeaway of all this rambling is there is no logical reason to make every folder you create a shared folder. For one thing, it makes your Plex yml much shorter.

Same here (been doing it that way for a while)...

I have 5 shares...

AppData (for my /config folders)

Home (for home directories)

Torrents (that's where torrents get downloaded

Disk_# (where everything else is)

docker (where container data is stored)

Then usually at CLI, I make a Data and Media directory under Disk_#. After I set up my symlinks under "/NAS" I literally have every path I need for a stack/compose file memorized and don't really need to look at them.

Only one of those folders I need shared over the network is Disk_#.. so that I share that folder over nfs.

Zitat von KM0201

After I set up my symlinks under "/NAS" I literally have every path I need for a stack/compose file memorized and don't really need to look at them.

Same here. I create a folder “/sym” and then create a symlink for each disk so that I can easily remember volume paths in compose:

/sym/disk1/appdata
/sym/disk1/media
/sym/disk2/rsnapshot-backup
/sym/disk1/rsnapshot-source

And when naming folders I always stick with lower case so I don’t accidentally wind up with “Appdata” and “appdata” and can’t figure out why my container doesn’t work right.

Zitat von Agricola

Same here. I create a folder “/sym” and then create a symlink for each disk so that I can easily remember volume paths in compose:

Code

/sym/disk1/appdata
/sym/disk1/media
/sym/disk2/rsnapshot-backup
/sym/disk1/rsnapshot-source

And when naming folders I always stick with lower case so I don’t accidentally wind up with “Appdata” and “appdata” and can’t figure out why my container doesn’t work right.

Yep... I tell people all the time with this there is no right or wrong way, so long as you are consistent.

Zitat von oldun1961

Thanks a lot for all the help.

Sorry I have taken so long to reply but I have been very busy, on holiday and then caring for a wife with covid-19

I now have a better idea about folder structure but I am still confused about how the paths to the folders are defined under Volumes in Portainer. However, as a complete noobie, I find it rather confusing to be given all instructions for OMV 5 when UI am using OMV 6. It not so easy, to me anyway!, how to find the relevant sections in OMV 6 when every instruction refers to OMV5. However I will persevere and i will get there in the end.

I now believe that the paths the the relevant plex folders are relative paths but relative to what!

Lets assume that I have a drive sda which is separate from the drive containing the Pi OS and OMV etc. The drive sda has the file system sda1.

On this disk I have created folders appdata and data, the latter being shared).

In data I have created a folders called plex

In plex I have created folders called tv, movies, videos, movies etc

Where do I create config? In a sub folder in appdata or in data?

What defines the base drive or folder for the relative paths and how do I enter this information to container called plex?

What is the relative path to movies?

Is it just /data/plex/movies? If not where will I find the required path?

As you can see I have a long way to go before really understanding this process.

Cheers

Alles anzeigen

I personally put any config directory, under appdata. That is all I put there.

Zitat von oldun1961

My next question is how and why should I use stacks?

As Zoki said its called stacks in Portainer and docker-compose.yml if you are using it in the command line.

A docker compose file contains a set of instructions that happens to be relatively easy to read by a non coder, that tells docker how to compile the container. If you have a problem and you post that docker compose file on this forum just about anybody who has created a container using docker compose can easily see where the problem is and thus help you build a successful container.