From 2a8e5d49524035699db968c62ebc5e64262a28b8 Mon Sep 17 00:00:00 2001 From: "Gan, Jimmy" Date: Sat, 4 Apr 2026 01:52:58 +0800 Subject: [PATCH] fix: stop then up instead of force-recreate force-recreate still tries to disconnect/reconnect networks which fails. Use stop then up - compose will detect the image changed and recreate the container automatically without network issues. --- .gitea/workflows/deploy-dev.yml | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/.gitea/workflows/deploy-dev.yml b/.gitea/workflows/deploy-dev.yml index fa579c1..ec28afd 100644 --- a/.gitea/workflows/deploy-dev.yml +++ b/.gitea/workflows/deploy-dev.yml @@ -65,5 +65,6 @@ jobs: run: | export DOCKER_API_VERSION=1.43 cd /nas-dashboard - # Force recreate container with new image (doesn't disconnect from networks) - docker compose -f docker-compose.dev.yml up -d --force-recreate --pull never + # Stop container, then start with new image (compose will recreate if needed) + docker compose -f docker-compose.dev.yml stop dashboard-dev + docker compose -f docker-compose.dev.yml up -d --pull never