To build a new version with a new release of a Tailscale image, simply create a new branch with the name of the Docker tag (ie. 'v1.72.1'). See tags here..
This addresses Tailscale Issue 8027.
Tailscale Docker Mod is great and I rely/relied heavily on it.
(+) Plug and play
(+) Easy configuration
(-) Confined to linuxserver.io images
(-) Installing software into a running container all the time felt dirty
(-) The above installation process took time (although it was quick)
The first-party Tailscale container was great but it didn't have a great way to
run tailscale serve.
(+) Very minimal image without S6 overhead
(+) Easy to configure as a sidecar container instead of an in-container install
(+) "Compatible" with any other networked service
(-) Running tailscale serve required creating, maintaining, and uploading JSON
files to a server
So, I tried to merge the two. This solution still has some limitations of the Docker Mod. Mainly, it only serves HTTPS on 443 externally. This covers 99% of my use cases. It can forward to whatever desired internal port.
As this wraps the 1st party solution, everything documented here should work.
Additionally, the following are required:
-
TS_SERVE_PORT (equivalent to
TAILSCALE_SERVE_PORTin Docker Mod) -
TS_SERVE_MODE (equivalent to
TAILSCALE_SERVE_MODEin Docker Mod) -
TS_FUNNEL (if set,
tailscale funnelis ran instead oftailscale serve)