trurl

If you compare that screenshot with the previous one, you will see that in the area below the textbox where it has the words "Container Path" in orange lettering, Jackett has /downloads, for example, but similar places on your other screenshot there is nothing next to "Container Path" for many of those. For example, for the host path /mnt/user/Storage/movies, there is nothing next to "Container Path". If you really want to learn, please do as I said and look at that link to the Docker FAQ I already gave. Then you will know what we want you to give us whenever you have any docker problem (at the first link in the FAQ), and you will be able to ask better questions if you at least try to understand the "Getting Started" stuff. The questions you are asking now are really just kind of random.

Without a container path, there is no way for the application to access the storage specified by the host path. I am surprised you aren't getting an error trying to start the docker with the settings in your screenshot. Depends. What is the Use cache: setting of your Docker user share? If you don't understand what is wrong with the settings in your screenshot, then you obviously don't understand volume mapping. Please see the first link in the Docker FAQ. It will tell you what we need to help you. Then read at least the "Getting Started" portion of the Docker FAQ. Link to Docker FAQ: https://lime-technology.com/forums/topic/57181-real-docker-faq/

This is probably only temporary until it fills up again. 20GB would likely be plenty if you had things setup correctly. You need to figure out why it is filling up. See "Docker Image Filling Up" in the Docker FAQ: https://lime-technology.com/forums/topic/57181-real-docker-faq/

How did you update? The correct way to update this docker is to restart it. You should never update from within the application. Have you tried restarting the docker? If you had it setup correctly then there should be no reason to go back to an older version.

yes, preclear writes a "clear signature" to the disk so unRAID will know.

If you need any help troubleshooting, there are plenty of helpful people in this forum. Post in the thread for the version you are using. See the very first link in the Docker FAQ for the information we will need to better understand your settings. https://lime-technology.com/forums/topic/57181-real-docker-faq/

Not sure what but you definitely have something not working normally. Most people never get that warning with only 20GB docker image.

And binhex plex is the other most used and most recommended, and lots of people are not having problems with it either. There are ways to start over in this drastic manner, but it shouldn't be necessary and likely to end up in the same place. It is nearly impossible to screw up your entire unRAID install by playing with dockers, simply because unRAID doesn't really install like other systems you may be familiar with. It just unpacks the OS clean and fresh from the archives on flash into RAM on each boot. Fixing the mistakes you are making in setting this up is the best approach. Do you have any other working dockers? What are you using as a guide to set these up? Have you read the Docker FAQ?

That's the one I (and many others) have been using for a very long time, and the one I recommend. What problems were you having? Did you ever get it to work at all? If not then it is almost certainly a user error.

What other version were you using? Most likely whatever problems you were having were user error. Most people change away from the limetech version since others are more up-to-date and better supported.

Did you read the post just before yours? The one ninthwalker posted today which said don't use the v2 beta?

It's very unlikely the dockers will be affected by downgrade, but also unlikely downgrade would solve anything. Saving data in the array is a pretty normal thing to do in general, so I don't understand your question.

According to your volume mappings, the application will see the unRAID folder /mnt/disk1/downloads at the container volume /downloads. The application doesn't know anything about the host paths, it only knows about the container volumes. Since that is probably only the beginning of things that may give you further trouble, I suggest you read through the Docker FAQ: https://lime-technology.com/forums/topic/57181-real-docker-faq/

And, in fact, this is the script thread we are on.

I think the main concern from the original author of the script was really more about people other than him taking responsibility for any modifications they made. And in some sense that problem never went away, with people asking for plugin support on the script thread and vice versa. Probably some of those old threads should just be locked.

Not according to their diagnostics.

Most of the plugins and dockers are provided by users like yourself (possibly even IT pros), completely without compensation except possibly in the form of donations from other users. And the vast majority of support provided on the forum is also provided by users like yourself (see above). We are mostly all volunteers here. If you would like to volunteer to support the plugin I'm sure other users would be grateful. Limetech is a very small company and concentrate on core functionality, but they have a lot of enthusiastic users who volunteer their time and effort to produce extensions, apps, help and advice to the rest of the user community.

Could you post the exact script that produced this output? I am wondering if you haven't tried but failed to type the script that kizer gave.

Maybe you're having disk I/O problems. Anything else in the syslog? Or maybe you have a ridiculous number of bait files? Did you have it putting bait in plex appdata or something?

this^

Impressive, but what I meant is we will still get questions about preclear. And everything else of course. I have seen lots of questions asking why they are getting a warning from FCP, and how do they fix it, when the warning actually already answers those questions.

And preclear plugin of course.

If you have an adblocker installed whitelist your server. Also, instead of just the syslog we would always very much rather have the complete diagnostics zip which you can download by going to Tools - Diagnostics. The diagnostics zip contains syslog and many other things which help us make sense of your situation.

this^

You don't need VPN to allow access to Plex.