tailscale-dev/docker-guide-code-examples

https://tailscale.com/blog/docker-tailscale-guide

tailscale-dev/docker-guide-code-examples

This repository supports:

• YouTube video
• Blog post

docker-guide-code-examples's Issues

Container connection fails if Tailscale is running on the host

I would like to set up the Immich stack as a Tailscale node, similar to the https://github.com/tailscale-dev/docker-guide-code-examples/tree/main/05-ts-immich-gpu example.

However, if I have Tailscale running on the host machine (which is running the Docker images), the Tailscale connection of the docker container never initializes. AFAICT, the DNS setup is misconfigured somehow and the container can not resolve any names, including the Tailscale DERP servers.

The host Tailscale server is configured to accept DNS from the admin panel, but turning that off did not resolve the issue. Only turning off the host Tailscale server allowed the Immich container to join the Tailscale network.

Example with multiple services

This is very cool and useful! - thanks for putting this together.

It would be very helpful to see an example of this applied to a more complex docker compose set-up. I've got a docker compose stack with multiple components: a database, a back-end server component and a web front-end. Previously I used networks: to add them to the same network and ports: to specify which ports they should expose to each-other but networks and ports are mutually exclusive with network_mode. Is there a suggested approach to using the tailscale container for a scenario like this?

healthcheck - when side docker starts

I created a docker compose file with tailscale and another docker (litellm).
It seems tailscale takes a bit longer to start and it is causing a name resolution issue when litellm starts (so it exits). Maybe there is another issue on top.

However, would it be possible to get in the example (docker-compose.yml) a section with:
An healthcheck we can add to the ts-docker (maybe a ping to the hello service) to confirm it started (above all the 1st time when it needs to validate the token?). I am not sure about the best way to do it?

was TS_SERVE_CONFIG removed?

I've recently tried to use your docker image with TS_SERVE_CONFIG, following the official docs and these examples, but after a bunch of testing with it, I concluded that it seams to me as though the environment variable TS_SERVE_CONFIG is no longer considered, and may have been removed by an update.
Most of my testing was done on 1st & 2nd June 2024, using the stable tag.

If I am correct, it would be great if both this repo as well as your official docs could be adjusted to reflect this, to spare others the trouble of attempting to get results out of using this environment variable.

"target":ip

I can not find any information on the "target" IP?
Is the ip in the example file an ip that work for everyone, or do you have to match it to your specific setup?

	"nodeAttrs": [
		{
			// Funnel policy, which lets tailnet members control Funnel
			// for their own devices.
			// Learn more at https://tailscale.com/kb/1223/tailscale-funnel/
			"target": ["autogroup:member"],
			"attr":   ["funnel"],
		},
		{"target": ["100.71.14.42"], "attr": ["funnel"]},
	],

Funnel not working

I sued the same compose file as shows in the example with tailscale as the sidecar proxy and mealie as the service that is being proxied. I used an Auth key and have the same container tag setup in my ACL. The serve function works but the funnel will not work.