From 2f65691e153506be26df04fd3e91340e9daf1419 Mon Sep 17 00:00:00 2001 From: "Gan, Jimmy" Date: Sat, 4 Apr 2026 02:05:09 +0800 Subject: [PATCH] fix: use docker rm -f pattern from working claude-dev workflow Replicate the proven approach from deploy-claude-dev-dev.yml: - Use 'docker rm -f' to completely remove the old container - Let compose create a fresh container from scratch - Avoids the 'stop then recreate' flow that fails with network errors This works because Docker Compose handles initial network connection during 'up' differently than reconnection during recreate. The rm -f approach succeeds even from the workflow container context. --- .gitea/workflows/deploy-dev.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/.gitea/workflows/deploy-dev.yml b/.gitea/workflows/deploy-dev.yml index ec28afd..362b679 100644 --- a/.gitea/workflows/deploy-dev.yml +++ b/.gitea/workflows/deploy-dev.yml @@ -65,6 +65,6 @@ jobs: run: | export DOCKER_API_VERSION=1.43 cd /nas-dashboard - # Stop container, then start with new image (compose will recreate if needed) - docker compose -f docker-compose.dev.yml stop dashboard-dev + # Remove old container completely, then create fresh + docker rm -f nas-dashboard-dev || true docker compose -f docker-compose.dev.yml up -d --pull never