Join GitHub today
Build #137 has some DNS / tracker connectivity issues #49
Host OS: Debian 9 (OMV 4 default)
I am updating my containers with watchtower. Today, build 137 was pushed on Docker Hub and I noticed my torrents were down with the tracker status 'name: tracker unavailable' for all possible trackers. I verified and trackers were up and running and were accessible from any other client. Both container, host and hypervisor clocks are in sync and updated by NTP hourly.
I tried restarting the container and the VM hosting Docker. Neither bore any results - after restart all trackers were slowly polled and were unreachable. From the container I can ping any trackers so it doesn't seem to be a network connectivity issue. I have not tried other operations.
Considering these I rolled back to build 136. Startup with previous configuration had no issues, all my settings were retained. After everything loaded, all tracker statuses were back to normal 'name: Announce OK'.
[INFO ] 10:46:21 server:650 Starting server in PID 210.
rollback to the version 136, everything is fine
all versions above 136 (137,138,139) doesn't work for me, because the daemon (deluged) won't start.
EDIT: the only thing i discovered is the following difference (all versions since 136 have the same code base); but the transmission image have the same "missing hostname" and works...
Still the same problem with the version 140 (same if I add missing conf file):
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
User uid: 911
[cont-init.d] 10-adduser: exited 0.