From 8514d5ea4b259213db57eddce17aba855a7e11ef Mon Sep 17 00:00:00 2001 From: "Gan, Jimmy" Date: Sat, 4 Apr 2026 02:18:26 +0800 Subject: [PATCH] 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. --- .gitea/workflows/deploy-dev.yml | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/.gitea/workflows/deploy-dev.yml b/.gitea/workflows/deploy-dev.yml index 69b8dc3..c187451 100644 --- a/.gitea/workflows/deploy-dev.yml +++ b/.gitea/workflows/deploy-dev.yml @@ -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