I'm new to dockers and don't completely understand the technical fields I'm asked to complete when installing binhex's Plex docker.  I have read the post around it, but admittedly, even the explanations are a bit over my head.  My own setup is pretty "vanilla."  At the moment I only have NAS running with three shares:  1) Movies, 2) TV Shows, and 3) Important Data to Keep.  Could someone possibly walk me through what I should possibly be updating for the following fields when adding the binhex Plex docker:

 

1)  Template

2)  Network Type

3)  Container Volume, Host Path, and Access.  /config and /media are already there, but for example I'm not sure whether I should leave those as-is or change them.  /media seems to point to where my media is which leads me to believe I should be pointing to Movies and TV Shows shares, but again, I'm just not sure.

The noobie docker setup guide http://lime-technology.com/forum/index.php?topic=37732.0 would be a good place to start.  It actually uses Plex as an example.  Its dated as far as adding the container (you've already done that), but will be good for help with the mappings.  Its really only the paths you need to be concerned about.  Everything else (host) will stay the same as binhex has set it up.

 

You might also want to look at the Docker FAQ for some more explanations of the paths  http://lime-technology.com/forum/index.php?topic=40937.0

 

EDIT:  Since you're asking about "Template", I'm going to assume that you installed Plex through Community Applications.  The "Template" Field that appears at the top is not used at all when using Community Applications.  That field gets used if the plugin is NOT installed

 

That explained a lot.  Thanks.  The only thing I'm thrown on at the moment is how the guide explains what the path should be for /config.  Should that just be the path of where the docker image is located?  Mine is on the cache.  The guide seems to say that, but then something else as well.

That explained a lot.  Thanks.  The only thing I'm thrown on at the moment is how the guide explains what the path should be for /config.  Should that just be the path of where the docker image is located?  Mine is on the cache.  The guide seems to say that, but then something else as well.

The /config that you'll see in most containers are where the application is storing its data (the program itself is stored in the docker.img file you created when you enabled docker.

 

For docker, you generally make a CACHE ONLY share called appdata.

 

For the /config mapping, you would enter a host path of /mnt/cache/appdata/Plex

Got it.  Thanks.  I'm up and running now with Plex crunching.  I'm still learning just how these Dockers operate and I think I messed up a little when creating the docker image.  I thought all the apps information would be self-contained inside the docker image so things like Plex Metadata or Sab's downloads would also be contained in the docker image.  As a result I made the docker image 30 gigs.  This is probably way too big for the few apps I run on this server, but probably not a big deal since I store this kind of information on a 120 gig cache and I don't use the mover. 

 

Anyway, now that I see how Plex is crunching information and where it resides I guess things like Sab work in the same way.  The app itself stays inside the image, but files it might use like metadata and downloads are outside the docker image...correct?

Anyway, now that I see how Plex is crunching information and where it resides I guess things like Sab work in the same way.  The app itself stays inside the image, but files it might use like metadata and downloads are outside the docker image...correct?

Absolutely...  One huge, huge, huge advantage of this is that assume that after plex finishes processing your media you decide that you need the 30 gigs of space for something else and want to downsize it.  Not a problem.  Worst thing that happens is the containers redownload, but since the appdata resides outside of the img file, its all back up and running right away exactly the same way you left it.

Great to know.  Thanks for your help.