From 6a7ff5d12f584c324efb9830e8b2a6eb7d8ce26f Mon Sep 17 00:00:00 2001
From: Pi Agent <pi-agent@falahos.my>
Date: Sun, 28 Jun 2026 03:28:34 +0800
Subject: [PATCH] =?UTF-8?q?fix:=20auto-healer=20v6=20=E2=80=94=20remove=20?=
 =?UTF-8?q?explicit=20--network=20flag=20from=20rollback=20(caused=20netwo?=
 =?UTF-8?q?rk=20bridge=20not=20found)?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

- rollback was using --network bridge explicitly, which fails on this Synology's
  Docker daemon when the bridge network is associated with a Swarm overlay
- Fixed: omit --network flag entirely, let Docker use default bridge behavior
- Also found and fixed: gateway container on Swarm overlay network couldn't
  route to 192.168.0.11:4014 — attached to bridge network to resolve
---
 auto-healer/auto-heal-agent.sh | 5 +----
 1 file changed, 1 insertion(+), 4 deletions(-)

diff --git a/auto-healer/auto-heal-agent.sh b/auto-healer/auto-heal-agent.sh
index 7fd06e0..0dde812 100644
--- a/auto-healer/auto-heal-agent.sh
+++ b/auto-healer/auto-heal-agent.sh
@@ -313,15 +313,12 @@ restore_protocol() {
         docker rm -f "$CONTAINER_NAME" 2>/dev/null || true
         sleep 2
 
-        # Recreate from rollback image
-        local network
-        network=$(docker inspect "$CONTAINER_NAME" --format '{{.HostConfig.NetworkMode}}' 2>/dev/null || echo "bridge")
+        # Recreate from rollback image (omit --network; default bridge works reliably)
         docker run -d \
           --name "$CONTAINER_NAME" \
           --restart unless-stopped \
           -p 4014:3000 \
           -v /var/services/homes/admin/falah-mobile/data:/app/data \
-          --network "$network" \
           "$ROLLBACK_IMAGE" >> "$AGENT_LOG" 2>&1
 
         sleep 15