I've been using this container for at least a year, without issue. Then my watchtower updated to the most recent build (2 days old)
Current build (latest) is giving me DNS errors with PIA servers. I swapped DNS providers (Cloudflare, Google) to no avail. I recreated the container, same problem. I tried current build of arch-rtorrentvpn with the same errors. I changed PIA servers (swiss, montreal, etc). Tried toggling with port forwarding on and off. No difference.
I created a new container with the arch-rtorrentvpn container with the previous build (0.9.7-1-07) and it worked*. Just did the same with arch-delugevpn back to 1.3.15_14_gb8e5ebe82-1-11 and it also works. The latest builds seem to be causing DNS errors with Synology DSM docker. I reloaded the old docker settings without issue on the manually specified build, so it doesn't seem to matter if it's from scratch or existing, the old builds work. New ones do not. ?
2018-08-07 22:12:57,733 DEBG 'start-script' stdout output:
[info] Adding 1.1.1.1 to /etc/resolv.conf
2018-08-07 22:12:57,741 DEBG 'start-script' stdout output:
[info] Adding 1.0.0.1 to /etc/resolv.conf
2018-08-07 22:12:58,006 DEBG 'start-script' stderr output:
random.c:102: fatal error: RUNTIME_CHECK(ret >= 0) failed
2018-08-07 22:12:58,018 DEBG 'start-script' stdout output:
[crit] swiss.privateinternetaccess.com cannot be resolved, possible DNS issues
2018-08-07 22:12:58,018 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 140398907495416 for <Subprocess at 140398907496280 with name start-script in state RUNNING> (stdout)>
2018-08-07 22:12:58,019 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 140398907495056 for <Subprocess at 140398907496280 with name start-script in state RUNNING> (stderr)>
2018-08-07 22:12:58,019 INFO exited: start-script (exit status 1; not expected)
2018-08-07 22:12:58,019 DEBG received SIGCLD indicating a child quit
*rutorrent has always been a problem with Synology DSM docker. I think Flood worked fine, but I needed the added functionality of full rutorrent (such as ratio groups), or Deluge and it's plugins. Regular rutorrent worked fine at first, restarting it stopped working (that or I lost patience). I figured either way, the inherent problem is the current builds for both containers. So I didn't waste any more time trying to get rutorrent to work (likely it's that DSM's AppArmor thing again), and that's outside the scope of this thread.