sparklyballs

if your webui password resets when you update the docker image, then i would expect that you're not mounting the config volume locally....

the logs are mounted locally in the volume mount for config, if you're docker.img is filling up then you either are not mounting the config files or the image is downloading into the image file. on a side note, if your image is filling up when the docker log is ~500 mb , you have bigger problems and need to expand the size of the docker.img. post screenshots of your volume mountings from the unraid webui and the Downloads section of the webui preferences for deluge itself.

i'm really confused what you're asking for here. you say an update from 5.6 beta 4 to 5.6 beta 1, that's going backwards surely ?

screenshots from latest version of this image...l

you need to ask this on the jackett github page. we don't make the app itself, we just package it in a docker image.

I think you may be able to change the port by looking at /config/qBittorrent/qBittorrent.conf and specifically the line Connection\PortRangeMin=6881

The underlying image should be updated, at the very minimum whenever an update nextcloud is released and preferably more regularlry. In the case of version changes to nextcloud, there may be changed/additional dependencies. On the subject of more regular refreshes, if there is a security issue with one of the dependencies or an update to say nginx or php for example, just updating the app in an existing container will not pick those up.

just fyi, it doesn't work....

As j0nnymoe has already said, updating the image does not update the version of nextcloud.

update via the webui, the nextcloud files are stored in the volume mount. this one of the very few exceptions where we say update via the webui.

Can't read anything at the bottom of the page at all. murky grey on black , i can see there are words there, but they might as well be heiroglyphics when it comes to deciphering the strange symbols.

if you can't write to the appdata share, you either have local drive issues or permissions are wrong.

https://github.com/rakshasa/rtorrent/wiki/rTorrent-0.9-Comprehensive-Command-list-(WIP)#comprehensive-list-of-rtorrent-09-commands

https://www.google.com/search?client=safari&rls=en&q=system.method.set_key+rtorrent&ie=UTF-8&oe=UTF-8

Just added note to the first post on how to resolve this.