After a restart, the container starts, but not transmission. OpenVPN is not working.

[emk2203]

I had the container run successfully and without intervention running for years, on an Arch system with really frequent updates.

Due to this unfortunate design decision, the PC restarted a lot. This was never a problem. After the initial start, each subsequent restart would also start docker, the container and everything within.

This has changed as of recently. After a restart, the container starts to run, but OpenVPN cannot establish a VPN.

Inside the container (with docker exec -it emk2203-transmission-1 bash), a ps aux gives

root@f696c770a817:/# ps aux
USER         PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
root           1  0.0  0.0   2640  1236 ?        Ss   07:28   0:00 dumb-init /etc/openvpn/start.sh
root           7  0.0  0.0   4360  3016 ?        Ss   07:28   0:00 /bin/bash /etc/openvpn/start.sh
root          19  0.0  0.0  93116  9804 ?        S    07:28   0:00 curl -sSL --cookie /dev/null https://www.privateinternetaccess.com/openvpn/openvpn.zip -o /tmp/tmp.R23J
root          31  0.3  0.0   4624  3536 pts/0    Ss   07:30   0:00 bash
root          43  0.0  0.0   7060  2868 pts/0    R+   07:30   0:00 ps aux

and a docker ps results in

CONTAINER ID   IMAGE                          COMMAND                  CREATED      STATUS                     PORTS                                                   NAMES
f696c770a817   haugene/transmission-openvpn   "dumb-init /etc/open…"   2 days ago   Up 3 minutes (unhealthy)   8118/tcp, 0.0.0.0:9091->9091/tcp, [::]:9091->9091/tcp   emk2203-transmission-1

After a docker-compose down, a docker-compose up starts the container successfully (standard log of startup omitted).

ps aux from inside the container shows

root@877571048f79:/# ps aux
USER         PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
root           1  0.0  0.0   2640  1264 ?        Ss   07:42   0:00 dumb-init /etc/openvpn/start.sh
root           7  3.0  0.0  13488  9580 ?        Rs   07:42   0:20 openvpn --script-security 2 --route-up /etc/openvpn/tunnelUp.sh --route-pre-down /etc/openvpn/tunnelDow
root          87  0.0  0.0   4492  3188 ?        S    07:42   0:00 /bin/bash /etc/openvpn/pia/update-port.sh
abc           93  3.3  0.1 796800 30724 ?        Ssl  07:42   0:22 /usr/local/bin/transmission-daemon -g /config/transmission-home --logfile /config/transmission-home/tra
root         193  0.0  0.0   2788  1496 ?        S    07:43   0:00 sleep 900
root         396  0.5  0.0   4624  3760 pts/0    Ss   07:54   0:00 bash
root         408  0.0  0.0   7060  2872 pts/0    R+   07:54   0:00 ps aux

A logfile from transmission is empty.

I had removed the container and tried pulling it and also pulling the dev version, but there are no differences. I need to start with the container not running and then enabling it manually in any case, or pull the container and start from zero.

Any ideas how to get back to running without manual intervention at PC restarts needed? If there is need for furhter analytics, please let me know.