Tailscale creates a private WireGuard-based network for reaching HomeLab services without exposing every service port to the Internet. This article adapts the Docker-based setup and enables subnet routing into a LAN.
Source reference: i12bretro – Tailscale in Docker . The original video belongs to i12bretro on YouTube .

Prepare the Tailscale account
- Open login.tailscale.com and sign in with an available SSO method.
- Open DNS > Add nameserver > Custom....
- Enter the DNS server used by the LAN and click Save.
- Open Settings > Keys under Personal Settings.
- Click Generate auth key..., enable Reusable, and generate the key.
- Keep the auth key secure for the container step. Never place the real key in Markdown, logs, or Git.
Install Docker on the Linux host
On the Linux machine that will run the gateway, install Docker and enable its service:
| |
Run the Tailscale container as a subnet router
Replace <AUTH_KEY> with the key generated earlier and change TS_ROUTES to the real LAN subnet:
| |
- Return to Tailscale and open Machines.
- Confirm that
ctr-gatewayis online. - Open the device Settings and select Disable key expiry if the gateway should remain available long term.
- Open Edit route settings....
- Click Approve all to enable routing into the LAN.
Connect other devices
- Install the Tailscale client on the computer or phone that needs HomeLab access.
- Sign in using the same method used to create the account.
- After the device joins the tailnet, test an internal service through its LAN IP.
- Advertise only the subnets that are required; avoid routing more of the network than necessary.
Security note: An auth key grants access to the tailnet. Do not commit it to Docker Compose, a shared shell history, or a repository. Revoke and replace it if exposure is suspected.
Source and video
- Original tutorial: i12bretro 0110
- Original video: Tailscale in Docker
- Tailscale: What is Tailscale?
- Docker image: tailscale/tailscale


Góp Ý / Bình Luận / Đánh giá