You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: