From 6d9c4f69cd57742050f4433ade1117a385ba0a8c Mon Sep 17 00:00:00 2001 From: Andreas Wrede Date: Sat, 19 Sep 2026 13:52:05 -0400 Subject: [PATCH] Fix DNS resolver after disabling systemd-resolved MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Root cause: /etc/resolv.conf was a broken symlink to systemd-resolved's stub resolver, which doesn't exist after disabling the service. Fixed by creating proper /etc/resolv.conf pointing to dnsmasq on 10.42.1.1 and upstream resolvers (1.1.1.1, 8.8.8.8). This fix allows apt-get to work again and enables podman installation. **Result: ✅ podman installed, homeassistant container starting** Co-Authored-By: Claude Haiku 4.5 --- HOMEASSISTANT.md | 19 ++++++++++++++----- 1 file changed, 14 insertions(+), 5 deletions(-) diff --git a/HOMEASSISTANT.md b/HOMEASSISTANT.md index 25d780c..af0c584 100644 --- a/HOMEASSISTANT.md +++ b/HOMEASSISTANT.md @@ -47,9 +47,18 @@ ESPHome setup deferred until network is more stable. When ready: 1. Copy `/srv/esphome` from old vanrouter (4.8GB) 2. Run ESPHome container on port 6052 -## Network Issue +## Network Fix Applied -The R5C has extreme latency preventing reliable package installation: -- Starlink connection appears unstable -- Consider when deploying production services -- May need to pre-download packages on local machine and transfer via USB +**Root Cause:** /etc/resolv.conf was a broken symlink to /run/systemd/resolve/stub-resolv.conf (which doesn't exist after disabling systemd-resolved) + +**Fix Applied:** +```bash +sudo rm -f /etc/resolv.conf +sudo sh -c 'echo nameserver 10.42.1.1 > /etc/resolv.conf' +sudo sh -c 'echo nameserver 1.1.1.1 >> /etc/resolv.conf' +sudo sh -c 'echo nameserver 8.8.8.8 >> /etc/resolv.conf' +``` + +This restores DNS resolution, allowing apt-get and podman image pulls to work properly. + +**Result:** ✅ podman now installs successfully, homeassistant container can pull image from ghcr.io