4 hours ago4 hr Overview: Support for Tetherd, a helper that keeps containers attached to the network of the container they route through.Application: Tetherd — https://github.com/Phil-Barker/tetherdDocker Hub: https://hub.docker.com/r/philbarker79/tetherdGitHub: https://github.com/Phil-Barker/tetherdDocumentation: https://github.com/Phil-Barker/tetherd/blob/main/docs/unraid.mdIf you run qBittorrent, Prowlarr, etc. through a VPN sidecar (ie.Network Type: container:gluetun), those apps lose their networking whenever the VPN container restarts or is recreated. They often still look fine on the Docker tab: up, correct network, no obvious error. They are just silently offline.Tetherd watches for that and repairs it. A restart of the VPN container is usually enough; it only rebuilds a dependent when the VPN container was actually recreated. Deliberately stopped containers stay stopped.Why this still exists on Unraid 7Unraid 7 can recreate a container that used container: networking, which made a lot of people hope a helper like this would go away. Two gaps remain.The common failure is a restart, not a recreate. Appdata Backup, a VPN client reconnecting, or docker restart gluetun keeps the same container ID and replaces the network namespace. Every dependent still looks correctly attached and is offline. Unraid does not detect that.The other gap is a VPN container that is running but not routing. The Docker tab shows it as up. Tetherd can use the image's own healthcheck (gluetun ships one) or an exec probe.InstallCommunity Applications listing is in progress. Until it appears, add this template URL:https://raw.githubusercontent.com/Phil-Barker/tetherd/main/templates/tetherd.xmlSet Provider to the exact name of your VPN/network container (GluetunVPN, gluetun, whatever docker ps shows). Restart policy: Unless Stopped.If you (like I did) previously had Rebuild-DNDC running, stop it first. Two helpers repairing the same containers will fight.After install:docker exec tetherd tetherd doctorThat is the first thing I will ask for if something looks wrong.The image talks to the host Docker socket and runs as root for the same reason Watchtower does. That is the product, not an oversight.Current version is v0.1.1. Early, but the behaviour above is what I built it for. Bug reports and “this container did something weird” are welcome here or on GitHub issues.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.