Since the latest (today) update, privoxy is failing to start. Here is the relevant log section:
[info] All checks complete, starting Privoxy...
2019-05-01T21:53:29.956623500Z
2019-05-01 21:53:29,957 DEBG 'privoxy-script' stderr output:
2019-05-01 21:53:29.957 7f0eef6eb140 Info: Privoxy version 3.0.28
2019-05-01 21:53:29.957 7f0eef6eb140 Info: Program name: /usr/bin/privoxy
2019-05-01T21:53:29.957904700Z
2019-05-01 21:53:30,007 DEBG 'privoxy-script' stderr output:
2019-05-01 21:53:30.006 7f0eef6eb140 Fatal error: can't bind to 172.17.0.4 :8118: The hostname is not resolvable
2019-05-01T21:53:30.007208000Z
2019-05-01 21:53:30,007 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 139932369015472 for <Subprocess at 139932368914976 with name privoxy-script in state RUNNING> (stdout)>
2019-05-01 21:53:30,007 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 139932368390128 for <Subprocess at 139932368914976 with name privoxy-script in state RUNNING> (stderr)>
2019-05-01 21:53:30,008 INFO exited: privoxy-script (exit status 1; not expected)
2019-05-01 21:53:30,008 DEBG received SIGCHLD indicating a child quit
2019-05-01 21:53:30,231 DEBG 'start-script' stdout output:
[info] Successfully retrieved external IP address 172.98.67.33
No changes in the startup or otherwise -- it was working fine last night after the latest Docker update, right up until watchtower updated to the latest 2 hour old version.
Rolling back to the build from 3 months ago resolved the problem and restored network connection.