"key" : "TRANSMISSION_ALT_SPEED_TIME_DAY", "key" : "TRANSMISSION_ALT_SPEED_TIME_BEGIN", "key" : "TRANSMISSION_ALT_SPEED_ENABLED", "value" : "/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin" "cmd" : "dumb-init /etc/openvpn/start.sh", I can see all the data paths and config seems to be mounted the way it should, but for whatever it never actually starts the transmission-daemon. ![]() ![]() It uses what appears to be a default settings.json in /etc/transmission-daemon. I can't seem to figure what is supposed to start the actual transmission daemon because when I connect to a bash shell on the container I can see there is a transmission-daemon service I can start, but it doesn't use the environment variables to configure it. ![]() After discovering the NET_ADMIN permissions and adding that the container will start and it appears the tunnel starts fine, but transmission-daemon doesn't. Unfortunately after upgrading it the container wouldn't start. ![]() Little did I know that the only thing broken at the time was the ca.cert of ghostpath that could have been fixed with a custom profile and updating the NET_ADMIN. Before I really did any troubleshooting I had the bright idea of updating DSM to 7. I've had a long time running setup using docker on my Synology NAS to run the transmission-openvpn container just fine.
0 Comments
Leave a Reply. |