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.