https://github.com/lpasselin/tailscale-docker
Tailscale in Docker without elevated privileges
https://github.com/lpasselin/tailscale-docker
docker docker-compose tailscale vpn
Last synced: 3 months ago
JSON representation
Tailscale in Docker without elevated privileges
- Host: GitHub
- URL: https://github.com/lpasselin/tailscale-docker
- Owner: lpasselin
- License: mit
- Created: 2022-08-22T17:17:39.000Z (over 3 years ago)
- Default Branch: main
- Last Pushed: 2023-12-07T20:23:16.000Z (about 2 years ago)
- Last Synced: 2025-04-09T17:14:26.556Z (9 months ago)
- Topics: docker, docker-compose, tailscale, vpn
- Language: Shell
- Homepage:
- Size: 16.6 KB
- Stars: 57
- Watchers: 1
- Forks: 12
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# Tailscale in Docker without elevated privileges
See associated blog post:
**Set the TAILSCALE_AUTH_KEY with your own ephemeral auth key**:
## docker-compose
The examples detailed below are in the docker-compose folder.
By default, no state is saved. The nodes are removed from the network when the tailscale container is terminated. This means the ip address is never the same.
The `stateful-example` does save the tailscale node state to a docker volume.
Requirements:
- [docker-compose](https://docs.docker.com/compose/install/)
Usage:
````bash
export TAILSCALE_AUTH_KEY="your-key"
# set which project is used
export PROJECT_DIRECTORY="docker-compose/simple-example"
# Sart with rebuild if necessary:
docker-compose --project-directory=${PROJECT_DIRECTORY} up -d --build
# Show logs and tail (follow):
docker-compose --project-directory=${PROJECT_DIRECTORY} logs --follow
# Stop:
docker-compose --project-directory=${PROJECT_DIRECTORY} down
````
### simple-example
As explained in the blog post, uses a docker-compose service to add the container in the VPN.
### complex-example
Not complex but more complex than the simple-example.
A nginx layer is added. It manages two services in independent containers at urls `/service-one` and `/service-two`.
### stateful-example
Same as simple-example but uses a volume to save state. The goal is to be able to reuse the same tailscale hostname _and ip address_.
Useful in situations where the tailscale magic DNS cannot be used.
## K8S
Same as the simple-example but on kubernetes.
Requirements:
- [Kind](https://kind.sigs.k8s.io/docs/user/quick-start/#installing-with-a-package-manager)
- [Kubectl](https://kubernetes.io/docs/tasks/tools/)
Usage:
````bash
# Create cluster
kind create cluster --name tailscale
kubectl get nodes
# Deploy tailscale and demo webpage:
kubectl apply -f k8s/simple-example/deployment.yaml
# Delete cluster:
kind delete cluster --name tailscale
````