TheCowStir

Tonight I noticed that my Plex Docker had an update available. So being the cutting edge foolish person I am I updated and I seemed to have broke my main media mount point in the Plex docker. I used /data/Movies to mount to my unRaid share /mnt/user/Movies However after I updated I no longer saw any content in /data/Movies from Plex. I found that if I moved the mount to a different path, like /mnt/Movies I could access media again. After using the "update" button in the docker page of unRaid do I need to clean something out, is there something broken with this version, or did I just get hit by a solar flare? My config was still intact so that mount was fine.

Ok, here is my quick start guide using gfjardim's template which makes the rest of the process look pretty simple (so far). The paths listed below assume that you are using user shares, if you aren't replace /mnt/user with /mnt/disk1 Click on the Docker tab. Where do you want to store the Docker image? If you have an SSD, put it there. This image will probably keep your drive from spinning down. Put that location in the Docker image text box with a file name. (The grey text is just a place holder so you can type there) I use /mnt/cache/docker.img (this docker.img file is like an iso file, and is actually mounted on your unRAID server.) Default image size, keep it at 10GB, read in the forums for reasons to increase it. Template repositories, this is what makes docker easy for us unRAID users, you can find a few template repositories throughout the forum, but a pretty good place to start is gfjardim's https://github.com/gfjardim/docker-containers/tree/templates Click Save. Then click start Click the Add button (The big green circle with a plus in it) Drop down the Template selection and select Crashplan Since everyone should be backing up data, I'll start with Crashplan. Read through the description Container volume is where you can access the Host Path inside the application Leave the /config line alone unless you really need to change it. (This is where Crashplan configuration files are stored) on /data Container volume set the Host path to /mnt/user Click Apply You should now have the Docker Container you just setup listed under Docker Containers. Notice there is an Autostart checkbox that you probably should check so you don't have to start the container everytime you restart your unRAID NAS. To finish setting up Crashplan, refer to this forum thread http://lime-technology.com/forum/index.php?topic=33864.0

How does this process change in beta 10? (I guess beta 8 or later is the same correct?)

<slaps forehead> the greyed out text is editable....

I'm trying to get started using Docker, however I'm starting at unRAID 6.0 Beta 10, and my interface around extensions/Docker looks different. (I upgraded a 5.05 install with Pro key to 6.0 beta 9, and upgraded to beta 10 tonight and started to configure my array (no configuration on the array prior). My docker section has a greyed out "Docker image:" path of /mnt/disk1/docker.img and the service is currently stopped and won't start. My end goal is to move from my existing unRAID 5.05 array to my new 6.0 array. Currently my old array is running Crashplan and Plex, which is what I would like to get running on the new array via Docker. Where do I start?

I am also one that would like IPv6 support. I run IPv6 support through HE.net tunnelbroker. Truthfully I don't care too much at this point if the core unRaid services support IPv6, however the additional things I use my unRAID server for I would like IPv6 for, like Plex. If the base OS isn't configured for IPv6 nothing else has a chance to work... I like the idea of IPv6 being an unsupported feature.