Feyo

Line 40 is the end of the file, so it sounds like some issue with an empty line or something maybe? I uploaded the file directly from my Unraid installation to this comment here. If that doesnt work, there must be something else broken. tailscale_container_hook.patch

Sorry for the late reply. I think the forum screwed up the patch formatting? Try this: https://gist.githubusercontent.com/p-rintz/34084acb3ce0dd0e504cc8e8f3403afa/raw/f331304c27ab36b60fc70418450ac4e257f92139/fix_tailscale_container_routing.patch

Hey there, thought I'd post my solution for this problem here, because I've been rather annoyed with it over the past few days and finally found a good solution. This issue affects you if you have a tailscale subnet router on the same network your containers are using. If so, if you use tailscale in your containers, you won't be able to actually reach your containers local ips anymore once they are online. Also explained (including the solution) in this tailscale KB article: https://tailscale.com/kb/1023/troubleshooting#lan-traffic-prioritization-with-overlapping-subnet-routes Anyway, getting the fix applied to a docker container isn't the easiest unless we patch the tailscale container hook. Which is what I'm doing here. If you have a need for this fix, you can find the patch here: tailscale_container_hook.patch Go to the /usr/local/share/docker/ directory and apply the patch via git apply /dir/with/tailscale_container_hook.patch You'll then need to add the "TAILSCALE_LOCAL_ROUTE" variable to your docker container you want the fix applied in like this: Next time you restart the container (or fully apply the variable), the fix will be applied. I've currently only tested it in debian/ubuntu containers to fully work. (arch based containers should also be fine) The fix relies on iproute2 being available, and while I try to install it automatically via the patch, I don't know if the package is called the same in apk based installs. So if its not, you'll see an error in your Container logs: "ERROR: ip command is not available." If so, tell me and Ill try to fix it. Other than that, this wont survive an Unraid reboot. You'll need to put this into a userscript or the like and apply it at boot.