The official Unraid Tailscale doc announces that some containers might not work with Tailscale. In my environment it's:

• Doublecommander

• Libreoffice

• Sqlitebrowser

All 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?

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:

• Doublecommander

• Libreoffice

• Sqlitebrowser

• speed stars

All 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.

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:

• Doublecommander

• Libreoffice

• Hollow Knight

• Sqlitebrowser

All 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.