Read the article, thnx
If I understand correctly, this is about reloading configuration instead of restarting container (downtime…).
Did try kill -s SIGHUP 1
Container log shows response to that: SIGHUP[hard,] received, process restarting
But it restarts/reloads, doesn’t quit/stop (also needs root access).
When exec in container using -u (UID) (so no root permission), only command that does something is kill -s SIGKILL -1. Don’t know what it exactly is doing, but it breaks the transmission web-interface (OpenVPN is still running).
Source (last few comments):
Can try to make ENTRYPOINT as suggested in link above (will be tomorrow I guess).
Also I was surprised by outcome when checked ps -aux :
root@OMV-2-ODROID:~# docker exec -ti -u 1000 TransmissionOpenVPN bash
abc@136b242136e9:/$ ps -aux
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
root 1 0.0 0.0 1584 320 ? Ss 14:45 0:00 /usr/bin/dumb-init /etc/openvpn/start.sh
root 11 0.0 0.2 8156 5352 ? Ss 14:45 0:00 openvpn --script-security 2 --up-delay…
abc 98 0.0 0.1 43028 2944 ? Ssl 14:45 0:00 /usr/bin/transmission-daemon -g…
abc 116 0.2 0.1 5220 3076 pts/0 Ss 14:51 0:00 bash
abc 121 0.0 0.1 7724 2840 pts/0 R+ 14:52 0:00 ps -aux
Seems like it runs as root (container started with UID and GID). dumb-init and openvpn do, transmission-daemon doesn’t… Is this normal behavior???
Tried with and without the –privileged flag (same result), which seems needed to be set as otherwise container exits with error in log: “permission denied” somewhere when setting up OpenVPN.
Which doesn’t make sense to me, doesn’t mention anything about that flag being needed: