Thank you for everyone’s help and input. I have it working now, albeit not in the way I had hoped (not using docker containers for it) but it works. I followed https://thedevquill.substack.com/p/setting-up-a-tailscale-exit-node but instead of using the NordVPN image I used the plain Wireguard client image. In the wireguard compose I set network_mode: container:wireguard. Now when I connect tailscale over the exit node, traffic is going out over the wireguard IP

The issue is that the remote server (the one I want to use as the exit node) doesn’t have tailscale on it. Otherwise I’d be doing just that :D

Thank you for the detailed explanation. I will give this a shot.

Sorry to be unclear Yes I want to be able to access my home services from outside over wireguard, but connect directly into the home network. However once connected to the home network I want all traffic to be routed outside via the remote wireguard server.

Jellyfin, navidrone, paperless, freshrss, mealie, linkwarden, and immich. All on a debian as docker compose setups on a home server. I access things via tailscale and if I need it outside of that via cloudflare tunnels. Simple and easy.

Personally I have the restraint they are talking about. It’s just laziness in disguise though

Elixir is a nice functional language. Not as purely functional as Haskel mind.

It is based off of Erlang and runs on the Erlang VM. Syntax is Ruby inspired. It is not a high performant language (like C, Rust, etc), but it excels at distributed computing and fault tolerance. There is excellent documentation and tooling for it as well.