fix: just restart container instead of recreating

Docker restart will use the new image that was just built. Avoids all the network reconnection issues from recreating the container. Simple and proven to work.
2026-04-04 02:18:26 +08:00
parent 431e2c0a5f
commit 8514d5ea4b
1 changed files with 2 additions and 3 deletions
@@ -64,6 +64,5 @@ jobs:
      - name: Deploy dev
        run: |
          export DOCKER_API_VERSION=1.43
-          # Execute deploy script on NAS host directly (not from workflow container)
-          # This avoids Docker-in-Docker network connection issues
-          ssh -o StrictHostKeyChecking=no zjgump@host.docker.internal "cd /volume1/docker/nas-dashboard && /volume1/@appstore/ContainerManager/usr/bin/docker rm -f nas-dashboard-dev || true && /volume1/@appstore/ContainerManager/usr/bin/docker compose -f docker-compose.dev.yml up -d --pull never"
+          # Just restart the container - it will use the new image
+          docker restart nas-dashboard-dev