July 31Jul 31 The official Unraid Tailscale doc announces that some containers might not work with Tailscale. In my environment it's:DoublecommanderLibreofficeSqlitebrowserAll other containers work as expect and I can reach them from my devices with their <containername>.tail* address.Is there an alternative way to get these containers to work with Tailscale?
August 17Aug 17 On 7/31/2026 at 1:24 PM, hawihoney said:The official Unraid Tailscale doc announces that some containers might not work with Tailscale. In my environment it's:DoublecommanderLibreofficeSqlitebrowserspeed starsAll other containers work as expect and I can reach them from my devices with their <containername>.tail* address.Is there an alternative way to get these containers to work with Tailscale?I’ve run into similar issues with containers that don’t behave well with Tailscale injection. One alternative worth trying is putting the affected containers behind a separate Tailscale sidecar or using a dedicated Docker network, rather than injecting Tailscale directly into each container. That can avoid networking conflicts while still allowing access through the tailnet. It may also be worth checking whether these particular images bind their services only to localhost or use unusual networking settings. Hopefully someone familiar with Double Commander, LibreOffice, and SQLiteBrowser can confirm the best configuration.
August 24Aug 24 On 7/31/2026 at 1:24 PM, hawihoney said:The official Unraid Tailscale doc announces that some containers might not work with Tailscale. In my environment it's:DoublecommanderLibreofficeHollow KnightSqlitebrowserAll other containers work as expect and I can reach them from my devices with their <containername>.tail* address.Is there an alternative way to get these containers to work with Tailscale?I’ve seen this with a few GUI-based containers too. One thing worth trying is running them through a Tailscale sidecar/container or using a dedicated network namespace, rather than relying on the container’s own Tailscale integration. That way the app itself doesn’t need to support Tailscale networking directly. It might be worth checking the container’s network mode and whether it binds only to localhost as well.
November 3Nov 3 On 7/31/2026 at 1:24 PM, hawihoney said:The official Unraid Tailscale doc announces that some containers might not work with Tailscale. In my environment it's:DoublecommanderLibreofficeSqlitebrowser block blastAll other containers work as expect and I can reach them from my devices with their <containername>.tail* address.Is there an alternative way to get these containers to work with Tailscale?You can try this: keep those three containers on the standard Docker Bridge network and access them directly through your Unraid host's Tailscale IP or MagicDNS name: https://<unraid-tailscale-name>:<port>. Maybe it's what you need now.
November 13Nov 13 Those three (Double Commander / LibreOffice / SQLite Browser) are often Desktop/GUI or multi-process images. Unraid’s Tailscale “injection” hooks the container network namespace; GUI stacks sometimes break when that remaps interfaces or DNS unexpectedly — which matches “most containers work, these don’t.”Practical alternatives that still get you a stable Tailscale address:1. Don’t inject into the GUI container. Run a small dedicated Tailscale (or `tailscale serve`/`funnel`) sidecar / separate userspace container on the same Docker network, then reach the app over the Docker bridge hostname/port from that sidecar. Keeps the app’s netns stock.2. Use Userspace networking / userspace-networking mode where available instead of full netns injection — slower, but avoids breaking apps that assume a normal eth0 + systemd-resolved style DNS.3. Expose only what you need with Tailscale Serve from the Unraid host (or a proxy container) to `http://container:port` rather than giving every container its own tailnet IP. For tools you open occasionally from a laptop, Serve is usually enough.4. Quick isolation test: temporarily disable injection on one failing container, confirm it works on the LAN IP again, then add Serve/sidecar. If LAN works and only injection fails, it’s almost certainly the netns hook, not the image itself.If you paste the container’s network mode (bridge/host/custom) and whether injection was set to “join” vs “userspace”, we can narrow which of the above fits cleanest.
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.