Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Never reconnects after network goes down #55

Open
ghost opened this issue Dec 4, 2022 · 0 comments
Open

Never reconnects after network goes down #55

ghost opened this issue Dec 4, 2022 · 0 comments

Comments

@ghost
Copy link

ghost commented Dec 4, 2022

I'm running rtorrent in Docker Compose and forcing its traffic over a VPN by running a VPN client in another container and then using network_mode: "container:vpn" on the rtorrent container. This is generally working, the torrent traffic is being routed via the VPN and, if the VPN container stops, rtorrent traffic stops (which is what I want).

The issue is that, when the network and VPN container are available again, rtorrent is never able to reconnect to anything. I need to restart the rtorrent container, and then everything is fine again. I had one thought to implement a healthcheck which, in conjunction with autoheal, would kill/restart the rtorrent container if it was unable to e.g. curl some site but, given the Docker image is based on scratch, it doesn't have any utilities like that in it.

Any ideas on how to resolve this? It seems like the root issue is that rtorrent should be able to reconnect after the network comes back, but this could also be solved in the Docker scenario by a healthcheck which fails if it can't connect to some test site on the internet.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

0 participants