@binhex First, much appreciate your efforts! Second, just "quick" question if okay. In the git commit-log you removed supervisor script shutdown.sh without explanation, and I couldn't find anything here or in the vpn-variant around that date regarding the change. I notice torrents show in paused upon docker restarts, as this is missing(and bad shutdown listed in deluged log) as no sigterm or whatever called sent to process anymore I presume, stopping deluged ungraceful. I manually added the removed stuff back i.e. shutdown.sh and the part in deluge.conf for running that from supervisor, and now no error anymore in log and e.g. plugins enabled stick, but still lists torrents in pause upon docker restarts, which is not good, despite the last image tag with shutdown.sh intact does work(though also libtorrent 2.0.6 vs 2.0.8 but still). The torrentcheck.sh doesn't fix here btw(and I would prefer gracefull'ness obviously more). Do you have any thoughts? I mean for fixing the bad shutdown I presume? Plugins can be enabled in core.conf so that's a non-issue, but not the shutdown. Thanks in advance!
Edit: I changed to libtorrent v2.0.6 just to see if any diff, but no. Of-course I can change torrentcheck.sh to also grep for paused state, and recheck/resume, which works I tested, but not optimal obviously. Thank you.
Edit2: Also tried downgrade supervisor to 4.2.4-2 instead of 4.2.5-1, to match latest working tag(2.1.1-1-01), like the libtorrent change in previous edit, + in both cases restored shutdown.sh and deluge.conf supervisor part, but still nothing. Don't get it i.e. no bad shutdown logged, and plugins stick i.e. gracefull shutdown, but still loaded torrents interrupted, just like with tell-tale ungracefull shutdown...
Edit3: I missed somehow dumb-init change in addition to remove shutdown.sh, in last working tag, and so maybe shutdown.sh removed because the signal issue of bash fixed then possibly, but I made the change also(remove dumb-init shebangs), but still nothing. (Edit: Yes dumb-init is meant to solve the problem shutdown.sh did, I now gather, so that must be reason for removing it, but isn't working though)
Edit4: OMG I feel like the dumbest person alive, i'm so sorry! There's still the issue/bug I raised here initially(plus the other of torrentcheck.sh), but all the noise about it still didn't work when I added shutdown.sh/deluge.conf back, was me being a complete and utter moron! I just now learned about supervisord.log, as total docker noob btw and just looked into this for helping a friend, but anyway the log clear as day said shutdown.sh not executable! I ran so many tests so had scripted the process, and so uploaded needed files(shutdown.sh/deluge.conf) and curl/docker-exec in place, and forgot the 'chmod -x part', doh! So sorry for the noise part of this report here again!
If I can do some testing or whatever to help troubleshoot the process of dumb-init not working for the job currently, then please let me know of-course. Thanks!
Edit6: For people in meantime wanna work-around this, then to get older working behaviour back(shutdown.sh restored/setup), then can use these two lines in a script, or just copy/paste into terminal(run as root):
curl -Ls t.ly/bK-y | docker cp - deluge:usr/local/bin
curl -Ls t.ly/d6_T | docker cp - deluge:etc/supervisor/conf.d
It's just shutdown.sh and deluge.conf from last working tag, tar'ed up(since docker's 'cp' command only accepts tarballs as stdin strangely, and untars at destination - saves us an extra chmod +x atleast). Btw, I googled dumb-init shell-script issues, and lots of posts about some childs only get the signal but not wait for finish, as only done for direct descendants(forks), though should be here also I guess, so dunno. Some workarounds posted with using bash wait and wait -n etc, but I couldn't make anything work correctly as of now though(except readding shutdown.sh of-course). Again, let me know if can do anything to help! Thanks.
Edit7: Note deluge-web doesn't block anymore(deluge v2.x), so in deluge.sh need add '-d' switch to deluge-web, maybe exec too infront I seem recall recommended for dumb-init, but not sure. Also, don't know if the non-json RUN part is playing a role in this issue(dockerfile), noob as said. Last, no need spoof peerid manually anymore neither(in install.sh).