I am encountering the following error on ZimaOS: “rename of /etc/resolv.conf to /etc/resolv.pre-tailscale-backup.conf failed (device or resource busy)”.
This error only shows up when I try to open Tailscale via the ZimaOS desktop screen, where it displays a “service unavailable” error.
Interestingly, my other Linux device is running Tailscale perfectly, and the issue is specifically happening when trying to open the app on ZimaOS.
That DNS message may not be the actual failure. It commonly occurs when /etc/resolv.conf is bind-mounted and cannot be renamed. Tailscale normally falls back to copying it instead.
The ZimaOS “service unavailable” message may instead mean the Tailscale container is stopped, unhealthy, or its WebUI port is unavailable.
Please run these commands from the ZimaOS terminal and post the complete output:
docker ps -a --filter "name=tailscale" --format "table {{.Names}}\t{{.Image}}\t{{.Status}}\t{{.Ports}}"
docker logs $(docker ps -aq --filter "name=tailscale" | head -n 1) --tail 100 2>&1
Please do not modify /etc/resolv.conf yet. The container status and logs should show whether the DNS warning is harmless or whether Tailscale is actually failing during startup.