MythEclipse/GMW
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

fix: force remove conflicting containers before docker compose up
Build & Deploy / build-and-push (discord-gateway) (push) Successful in 26s
Build & Deploy / build-and-push (backend) (push) Successful in 1m22s
Build & Deploy / build-and-push (proxy) (push) Failing after 3m26s

Browse Source 
docker compose down doesn't always remove containers that were
created with a different compose configuration. Add explicit
docker rm -f for all three containers before up.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
Developer
2026-07-28 07:13:00 +07:00
co-authored by Claude Opus 4.8
parent 995a704c52
commit c8975b6f6d
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.gitea/workflows/deploy.yml
+1 -1
View File
@@ -64,4 +64,4 @@ jobs:
ENV_B64=$(echo "$ENV_FILE" | base64 -w0)
ssh -o StrictHostKeyChecking=accept-new \
"$VPS_USER@$VPS_HOST" \
"cd /opt/imphenbot/infra/docker && echo '$ENV_B64' | base64 -d > .env && docker compose pull && docker compose down --remove-orphans && docker compose up -d --remove-orphans && docker image prune -f"
"cd /opt/imphenbot/infra/docker && echo '$ENV_B64' | base64 -d > .env && docker compose pull && docker compose down --remove-orphans && docker rm -f imphenbot-discord-gateway imphenbot-backend imphenbot-proxy 2>/dev/null; docker compose up -d --remove-orphans && docker image prune -f"