This project provides build and configuration information to run Tailscale in Mikrotik Container. Container is Mikrotik's own implementation of Docker(TM), allowing users to run containerized environments within RouterOS.
This project is only recommended for research and testing purposes. Testing indicates there are significant performance hurdles: running a unidirectional IPerf UDP test of 50 Mbps via the container on a Mikrotik hAP ac3 consumes ~75% of the router's CPU.
The instructions below assume a use case for tailscale-enabled hosts accessing a router connected LAN subnet. Both Tailscale and Headscale control servers are supported.
Other site to site scenarios are outlined in the project wiki.
The Mikrotik Container package is compatible with ARM, ARM64 and x86 architectures and the router must be be running RouterOS v7.6 or later. Refer to the Mikrotik Container documentation for recommendations, disclaimer and security risks.
The example container runs as a tailscale subnet router on a Mikrotik hAP ac3. There are two subnets configured:
- 192.168.88.0/24: the default bridge with physical LAN interface ports, routed to the tailscale network
- 172.17.0.0/16: the docker bridge with a virtual ethernet (veth) interface port for the container
A WAN interface is configured as per default configuration on ether1 for connectivity to the Tailscale Network.
Note storage of the docker image on the router uses a USB drive mounted as disk1 due to the limited storage (128MB) available on the router. To configure storage devices see the Mikrotik Disks guide.
Note: this step is only required if you are uploading a tar image file to your router as per Configuration Step 6b.
The build script uses Docker Buildx.
-
In
build.shset the PLATFORM shell script variable as required for the target router CPU - see https://mikrotik.com/products/matrix -
Run
./build.shto build the image. The build process will generate a container image archive filetailscale.tar
This section follows the Mikrotik Container documentation with additional steps to route the LAN subnet via the tailscale container.
- Enable container mode, and reboot.
/system/device-mode/update container=yes
- Create a veth interface for the container.
/interface/veth add name=veth1 address=172.17.0.2/16 gateway=172.17.0.1
- Create a bridge for the container and add veth1 as a port.
/interface/bridge add name=dockers
/ip/address add address=172.17.0.1/16 interface=dockers
/interface/bridge/port add bridge=dockers interface=veth1
- Enable routing from the LAN to the Tailscale Network
/ip/route/add dst-address=100.64.0.0/10 gateway=172.17.0.2
- Add environment variables and container mount
| Variable | Description | Comment |
|---|---|---|
| PASSWORD | System root user password | |
| AUTH_KEY | Tailscale non-reusable key, Oauth secret or Headscale pre-authenticated key | Generate from the Tailscale console or Headscale CLI |
| ADVERTISE_ROUTES | Comma-separated list of routes to advertise | |
| CONTAINER_GATEWAY | The container bridge (veth1) IP address on the router | |
| LOGIN_SERVER | Headscale login server | Only required for Headscale control server. Do not set if using Tailscale |
| UPDATE_TAILSCALE | Update tailscale on container startup | |
| TAILSCALE_ARGS | Additional arguments passed to tailscale | Optional. Note ---accept-routes is required to accept the advertised routes of the other subnet routers |
| TAILSCALED_ARGS | Additional arguments passed to tailscaled | Optional |
Example Tailscale control server configuration:
/container/envs
add name="tailscale" key="PASSWORD" value="xxxxxxxxxxxxxx"
add name="tailscale" key="AUTH_KEY" value="tskey-xxxxxxxxxxxxxxxxxxxxxxxx"
add name="tailscale" key="ADVERTISE_ROUTES" value="192.168.88.0/24"
add name="tailscale" key="CONTAINER_GATEWAY" value="172.17.0.1"
add name="tailscale" key="UPDATE_TAILSCALE"
add name="tailscale" key="TAILSCALE_ARGS" value="--accept-routes --advertise-exit-node"
Example Headscale control server configuration:
/container/envs
add name="tailscale" key="PASSWORD" value="xxxxxxxxxxxxxx"
add name="tailscale" key="AUTH_KEY" value="xxxxxxxxxxxxxxxxxxxxxxxxxxxx"
add name="tailscale" key="ADVERTISE_ROUTES" value="192.168.88.0/24"
add name="tailscale" key="CONTAINER_GATEWAY" value="172.17.0.1"
add name="tailscale" key="LOGIN_SERVER" value="http://headscale.example.com:8080"
add name="tailscale" key="TAILSCALE_ARGS" value="--accept-routes --advertise-exit-node"
Define the the mount as per below.
/container mounts
add name="tailscale" src="/tailscale" dst="/var/lib/tailscale"
- Create the container
The container can be created via the container registry (Step 6a) or using the tailscale.tar file generated by building the Docker image locally (Step 6b).
6a. Container registry
Configure the registry URL and add the container.
/container/config
set registry-url=https://ghcr.io tmpdir=disk1/pull
/container add remote-image=fluent-networks/tailscale-mikrotik:latest interface=veth1 envlist=tailscale root-dir=disk1/containers/tailscale mounts=tailscale start-on-boot=yes hostname=mikrotik dns=8.8.4.4,8.8.8.8
6b. Tar archive file
Using the file tailscale.tar generated by running build.sh, upload the file to your router. Below we assume the image has been uploaded to the router as disk1/tailscale.tar
/container add file=disk1/tailscale.tar interface=veth1 envlist=tailscale root-dir=disk1/containers/tailscale mounts=tailscale start-on-boot=yes hostname=mikrotik dns=8.8.4.4,8.8.8.8
If you want to see the container output in the router log add logging=yes to the container add command.
Ensure the container has been extracted and added by verifying status=stopped using /container/print
/container/start 0
In the Tailscale console, check the router is authenticated and enable the subnet routes. Your tailscale hosts should now be able to reach the router's LAN subnet.
The container exposes a SSH server for management purposes using root credentials, and can be accessed via the router's tailscale address or the veth interface address. Alternatively, you can access the container via the router CLI:
/container/shell 0
bash-5.1#
To upgrade, first stop and remove the container.
/container/stop 0
/container/remove 0
Create the upgraded container as per Step 6.
The script upgrade.rsc automates the upgrade process. To use the script, edit the hostname variable to match your container and import the script - note the script assumes the container repository is being used.
/system script add name=upgrade source=[ /file get upgrade.rsc contents];
Run the script:
/system script
run [find name="upgrade"];
Stopping the container...
Waiting for the container to stop...
Waiting for the container to stop...
Waiting for the container to stop...
Stopped.
Removing the container...
Waiting for the container to be removed...
Removed.
Adding the container...
Waiting for the container to be added...
Waiting for the container to be added...
Waiting for the container to be added...
Waiting for the container to be added...
Waiting for the container to be added...
Waiting for the container to be added...
Added.
Starting the container.
Note the script will continue to run if you are connecting over the tailnet. When completed, check the router is authenticated and enable the subnet routes in the Tailscale console.
We welcome suggestions and feedback from people interested in integrating Tailscale on the RouterOS platform. Please send a PR or create an issue if you're having any problems.