From f19b70d179e5b4ed6862417acb6efc68c19296df Mon Sep 17 00:00:00 2001 From: "Gan, Jimmy" Date: Sat, 4 Apr 2026 01:15:24 +0800 Subject: [PATCH] fix: use docker stop/rm instead of compose down for deploy docker compose down may have issues with external networks or project names. Use direct docker stop/rm commands instead. --- .gitea/workflows/deploy-dev.yml | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/.gitea/workflows/deploy-dev.yml b/.gitea/workflows/deploy-dev.yml index 4965658..054982a 100644 --- a/.gitea/workflows/deploy-dev.yml +++ b/.gitea/workflows/deploy-dev.yml @@ -64,6 +64,8 @@ jobs: - name: Deploy dev run: | export DOCKER_API_VERSION=1.43 - # Stop and remove old container, then create with new image - docker compose -f /nas-dashboard/docker-compose.dev.yml down || true + # Stop and remove old container if it exists + docker stop nas-dashboard-dev 2>/dev/null || true + docker rm nas-dashboard-dev 2>/dev/null || true + # Create new container docker compose -f /nas-dashboard/docker-compose.dev.yml up -d --pull never