From e396f77299b3e04326d9d328a6b0785f51a9bb27 Mon Sep 17 00:00:00 2001 From: "Gan, Jimmy" Date: Sat, 4 Apr 2026 01:36:18 +0800 Subject: [PATCH] fix: use --force-recreate to update container in-place This avoids disconnecting from networks which seems to cause issues when run from the workflow container. Force recreate updates the container without removing it first. --- .gitea/workflows/deploy-dev.yml | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/.gitea/workflows/deploy-dev.yml b/.gitea/workflows/deploy-dev.yml index 0707740..fa579c1 100644 --- a/.gitea/workflows/deploy-dev.yml +++ b/.gitea/workflows/deploy-dev.yml @@ -65,7 +65,5 @@ jobs: run: | export DOCKER_API_VERSION=1.43 cd /nas-dashboard - # Stop and remove container, then recreate with new image - docker stop nas-dashboard-dev 2>/dev/null || true - docker rm nas-dashboard-dev 2>/dev/null || true - docker compose -f docker-compose.dev.yml up -d --pull never + # Force recreate container with new image (doesn't disconnect from networks) + docker compose -f docker-compose.dev.yml up -d --force-recreate --pull never