Skip to content

When rebooting system, transmission container starts, but proxy doesn't #2844

Closed Answered by bassmadrigal
bassmadrigal asked this question in Q&A
Discussion options

You must be logged in to vote

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.

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:

docker compose -f location/to/transmission.yml up -d

Once I did that, I was able to confirm my restart settings using docker inspect for each container.

Replies: 1 comment

Comment options

You must be logged in to vote
0 replies
Answer selected by bassmadrigal
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
1 participant