From 466efdb873ecb9e8ae3dc29f105abded953eb1a5 Mon Sep 17 00:00:00 2001 From: Thomas Faour Date: Fri, 31 Jul 2026 12:35:14 +0000 Subject: [PATCH] Deploy: docker compose down before pull/up, not just up -d up -d alone assumes the previous container releases port 8420 cleanly before the new one binds -- it doesn't force that. The last three deploys all failed with "port is already allocated" at exactly that step; running compose down first (confirmed working when done manually over SSH) guarantees the old container is fully stopped and removed before the new one starts, closing the race. --- .gitea/workflows/server-docker-build.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.gitea/workflows/server-docker-build.yml b/.gitea/workflows/server-docker-build.yml index fa52267..19c1c76 100644 --- a/.gitea/workflows/server-docker-build.yml +++ b/.gitea/workflows/server-docker-build.yml @@ -69,4 +69,4 @@ jobs: ssh-keyscan -p "$DEPLOY_PORT" "$DEPLOY_HOST" >> ~/.ssh/known_hosts 2>/dev/null ssh -i ~/.ssh/deploy_key -p "$DEPLOY_PORT" -o StrictHostKeyChecking=yes \ espressoframe_deployer@"$DEPLOY_HOST" \ - 'cd ~/espresso-frame && docker compose pull && docker compose up -d' + 'cd ~/espresso-frame && docker compose down && docker compose pull && docker compose up -d'