CHBMB

Why did you use 146? It's seven months old. 5b398f77-ls22 would be the last pre v2 release. To fix your missing torrents I guess it would be restore from a backup.

@CorneliousJD Pull an older tagged release. https://hub.docker.com/r/linuxserver/deluge/tags

I cannot replicate any of the behaviour your describing so completely at a loss of what to tell you. It doesn't need removing. Working as far as I can tell. Sent from my Mi A1 using Tapatalk

Were you running a Windows 10 VM on your Ubuntu server? Quick scroll through the thread and it all seems to be indicating an issue with virtualisation of a Windows 10 install to me. Have you tried all the things people have suggested above? Specifically reducing the amount of RAM allocated to VMs? Sent from my Mi A1 using Tapatalk

Sounds like a hairpin NAT / NAT reflection issue to me Sent from my Mi A1 using Tapatalk

External Devices plugin Sent from my Mi A1 using Tapatalk

Ha! You found it....

This is covered in the first two posts

Clever.....

Nice to see a good guy! Just curious, how did you come upon it?

Awesome, thanks for taking the time to report it, it's a paper cut for sure.

I'm down with blaming Squid..... Sent from my Mi A1 using Tapatalk

What's your docker run configuration? (See the docker FAQ) Sent from my Mi A1 using Tapatalk

I have all my appdata and my docker.img mounted on an "unassigned device" and have done since I started using V6 of Unraid in 2015 I think it was. Sent from my Mi A1 using Tapatalk

Looks like I'm rethinking my plan.

Well, my plan was to just move it and hope for the best...... Wasn't really planning on constructing anything. I think it'll be ok.......

And here's me planning on migrating everything to the garage and worried it'll get too cold in the autumn/winter......

Sqlite database corruption has been an issue for SOME people using /mnt/user/appdata/ for a long time, however nobody has been able to isolate why it affects some users and not others. If you read what I wrote I didn't say using /mnt/disk1/appdata would fix an array being spun up all the time, but it stands to reason if you have a load of docker containers metadata then whilst those containers are running, applications will be accessing it, now if that data is spread across various array drives and not confined to a single disk, it MAY, keep drives spun up unnecessarily. Regardless using your protected array for your appdata isn't a great idea due to the performance hit on writing to the protected array, which is why I would always recommend using at least a cache disk or, even better, an SSD for this. Personally I have spinning rust as my cache disk as it's used as a recording/timeshift store for my PVR and I use a SSD mounted with unassigned devices to store my docker.img and appdata and noticed a massive difference with Emby and Plex in terms of webui responsiveness, compared with when it was on the cache disk. The downside to running everything on cache, or an unassigned device is of course no parity protection, however as parity is not a backup strategy, everyone should have mechanisms in place to ensure their appdata is regularly backed up so in the event of issues they have a recent source to restore from. I personally use CA backup/restore on a weekly basis for this, copying my backups to my protected array and then I rclone it to a cloud provider. Sent from my Mi A1 using Tapatalk

As a devout atheist I should know better..... Sent from my Mi A1 using Tapatalk

You don't have to find the problem, we've told you how to fix it. Regardless of whether you have a cache drive or not, ideally your appdat should be confined to a single disk (prevents keeping the whole array span up all the while) If that is disk1 disk2 or disk9 it doesn't matter. Use /mnt/disk1/appdata Same end result. Fixes the issue.

But that shows it running? Can you not get to the webui. Sent from my Mi A1 using Tapatalk

You're probably better looking at examples of how it's done. Dockerfile = uncustomised build that will be the same for everyone. Init stage = Where customisation happens, copying/linking stuff to persistent storage, ingesting environmental variables to change the way the container runs or functions.

I took a look out of curiosity, but those images are nearly two years old, so I decided I wasn't that curious.

OK, you're getting confused between what you do in docker versus what you do in the Unraid webgui. You add a port not a variable when you want to add a port to a Unraid template. Set the container port to whatever the container port is, then change the host port to whatever you want it to be.

You shouldn't set variables in the Dockerfile itself as a general rule, variables come into play at the runtime stage not the build stage. Might be helpful if you linked a Github repo or something, 'cos I'm not entirely clear what you're trying to do.