April 11, 20251 yr I have an issue getting Uptime Kuma behaving with Tailscale (CorneliousJD louislam/UptimeKuma from the Community Apps). I want to have that container connected to my Tailscale network so I could ping devices and track their up/down status. However whenever I try to enable the Tailscale integration for that container - it overrides (as far as I can tell) the Unraid tailscale state in /boot/config/plugins/tailscale/state Unraid is connected to Tailscale. When I launch that Kuma container with the Tailscale integration enabled for it - my Unraid Tailscale device hostname and config changes to that of the Kuma container one. No matter what path I choose in the containers Tailscale State Directory - it will not use it. It creates that folder on the container itself but the contents are empty. I assume it uses Unraids /boot/config/plugins/tailscale/state as it adds that containers certs to /boot/config/plugins/tailscale/state/certs, and as I mentioned - it changes the Unraid hosts config/hostname/etc to that of what should have been inside the container. This also caused an issue where the Unraid nginx service would start failing and I couldn't access the WebGUI anymore. Message from syslogd@Core at Apr 12 00:41:49 ... nginx: 2025/04/12 00:41:49 [emerg] 2974352#2974352: bind() to 100.81.178.103:443 failed (98: Address already in use) Message from syslogd@Core at Apr 12 00:41:49 ... nginx: 2025/04/12 00:41:49 [emerg] 2974352#2974352: bind() to [fd7a:115c:a1e0::a801:b267]:443 failed (98: Address already in use) I had to stop Tailscale on Unraid /etc/rc.d/rc.tailscale Delete the contents of /boot/config/plugins/tailscale/ rm -rf /boot/config/plugins/tailscale/* Restart Docker, disable the Tailscale integration in the Kuma container, do another round of stopping, deleting, etc. until I was finally able to launch the WebGUI and not have it crash. I used the exact same settings on my Grafana container and it works perfectly on Tailscale. Network type: Bridge Privileged: Off Tailscale Hostname: <whatever> Tailscale State Directory: <whatever> The rest of container Tailscale configuration options - default/no changes.
April 15, 20251 yr Solution I see the issue with this container. It has a mapping for "Docker Socket", but instead of mapping /var/run/docker.sock, it is mapping the entirety of /var/run. /var/run/tailscale/tailscaled.sock is the socket that Tailscale uses to communicate with itself. This means that the container is mapping the host socket into the container, which then causes the chaos you have encountered. If you remove the mapping for /var/run and replace it with one for /var/run/docker.sock, it should work better. (Or, if you're not using the Docker socket for anything, just remove the mapping.)
April 15, 20251 yr Author 4 hours ago, EDACerton said: I see the issue with this container. It has a mapping for "Docker Socket", but instead of mapping /var/run/docker.sock, it is mapping the entirety of /var/run. /var/run/tailscale/tailscaled.sock is the socket that Tailscale uses to communicate with itself. This means that the container is mapping the host socket into the container, which then causes the chaos you have encountered. If you remove the mapping for /var/run and replace it with one for /var/run/docker.sock, it should work better. (Or, if you're not using the Docker socket for anything, just remove the mapping.) Thank you for the reply and thank you for the solution! I removed the Docker socket mapping and it's working perfectly (from what I can tell) with Tailscale! Thank you!!
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.