From fa348efe2ac383ee49f3dc8500b9b03c9ecf5144 Mon Sep 17 00:00:00 2001 From: you Date: Fri, 17 Apr 2026 05:08:32 +0000 Subject: [PATCH] =?UTF-8?q?fix:=20force-remove=20staging=20container=20bef?= =?UTF-8?q?ore=20deploy=20=E2=80=94=20handles=20both=20compose=20and=20doc?= =?UTF-8?q?ker-run=20containers?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The deploy step used only 'docker compose down' which can't remove containers created via 'docker run'. Now explicitly stops+removes the named container first, then runs compose down as cleanup. Permanent fix for the recurring CI deploy failure. --- .github/workflows/deploy.yml | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/.github/workflows/deploy.yml b/.github/workflows/deploy.yml index 37291a28..761a4fbd 100644 --- a/.github/workflows/deploy.yml +++ b/.github/workflows/deploy.yml @@ -387,7 +387,10 @@ jobs: - name: Deploy staging run: | - # Stop old container and release memory + # Force-remove the staging container regardless of how it was created + # (compose-managed OR manually created via docker run) + docker stop corescope-staging-go 2>/dev/null || true + docker rm -f corescope-staging-go 2>/dev/null || true docker compose -f "$STAGING_COMPOSE_FILE" -p corescope-staging down --timeout 30 2>/dev/null || true # Wait for container to be fully gone and OS to reclaim memory (3GB limit)