When rebooting system, transmission container starts, but proxy doesn't #2844
-
I have the docker compose conf file pasted at the end of this post for transmission and its proxy. In it, (I think) I have specified for both transmission-openvpn and transmission-openvpn-proxy to restart unless-stopped. However, when my system is rebooted, transmission-openvpn restarts fine, but transmission-openvpn-proxy does not. I am relatively new to docker, so I might be missing something obvious. Maybe my conf file is put together incorrectly or there's some other configuration issue. It doesn't seem like it is a docker startup issue itself since transmission-openvpn starts up fine, so it seems to be an issue with this specific conf file. I will note that I added the proxy section about 5 months after I created the initial config file. I'm not sure if I'm supposed to run a command to update some internal docker config file with the new settings. Any help would be appreciated. (If not, it wouldn't be that hard to just add a command to my startup to restart these containers using the conf file, but I would love the proxy startup to be automatic like the transmission container itself).
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
This was the key problem. I found that docker compose won't update an already existing container, even if you use a changed transmission.yml to restart the container. I needed to recreate the containers using the new settings by running the following command:
Once I did that, I was able to confirm my restart settings using docker inspect for each container. |
Beta Was this translation helpful? Give feedback.
This was the key problem. I found that docker compose won't update an already existing container, even if you use a changed transmission.yml to restart the container. I needed to recreate the containers using the new settings by running the following command:
Once I did that, I was able to confirm my restart settings using docker inspect for each container.