This looks like a convenient solution! However, when trying to run compose it gives me the error: yaml: line 8: did not find expected key. Line 8 in my compose file is where the environment variables start. I added a newly generated auth key to TAILSCALE_AUTHKEY so I'm not sure why I'm getting this error. Any suggestions?
Edit: I moved the mod snippet to the top of the environment variables section and now I get the error yaml: line 8: did not find expected '-' indicator. I do have the '' - ' in place though. I am supposed to add the mod snippet to the environment variables of the delugevpn container, correct?
You can just specify that the docker's ports attach to the Tailscale IP address like this:
<tailscale-ip>:port:port for e.g. 100.34.89.23:80:80
The networking should be in the host mode, right?
What if it’s bridged, like connected to the network of a reverse proxy container?
Can you have one Tailscale instance on the host, accessing all containers instead of one side car container for each application container, like suggested here
I know I'm late to the party, but this might be the solution I'm looking for. In theory you would:
Install Tailscale on the machine running docker.
List "<tailscale-ip>:port:port" for the ports in the config file of each docker container.
Now you should be able to access the all the docker containers from a machine inside your tailnet without exposing any ports on the host machine? Also, you wouldn't have to do the service linking, correct?
This looks like a convenient solution! However, when trying to run compose it gives me the error:
yaml: line 8: did not find expected key. Line 8 in my compose file is where the environment variables start. I added a newly generated auth key toTAILSCALE_AUTHKEYso I'm not sure why I'm getting this error. Any suggestions?Edit: I moved the mod snippet to the top of the environment variables section and now I get the error
yaml: line 8: did not find expected '-' indicator. I do have the '' - ' in place though. I am supposed to add the mod snippet to the environment variables of the delugevpn container, correct?More replies
You can just specify that the docker's ports attach to the Tailscale IP address like this:
<tailscale-ip>:port:port for e.g. 100.34.89.23:80:80
The networking should be in the host mode, right?
What if it’s bridged, like connected to the network of a reverse proxy container?
Can you have one Tailscale instance on the host, accessing all containers instead of one side car container for each application container, like suggested here
https://tailscale.com/blog/docker-tailscale-guide
More replies
So under the ports section of the container (in the compose file) just add
- <tailscale-ip>:port:port? With the correct IP and port numbers ofc.More replies
I know I'm late to the party, but this might be the solution I'm looking for. In theory you would:
Install Tailscale on the machine running docker.
List "<tailscale-ip>:port:port" for the ports in the config file of each docker container.
Now you should be able to access the all the docker containers from a machine inside your tailnet without exposing any ports on the host machine? Also, you wouldn't have to do the service linking, correct?
More replies