From a19b20704363bffac2f8a3aede632eda68a2cd3c Mon Sep 17 00:00:00 2001 From: "Gan, Jimmy" Date: Sat, 23 May 2026 23:35:53 +0800 Subject: [PATCH] fix: remove conflicting docker-socket-proxy container before retry When docker compose --pull never fails due to network endpoint issues, the retry with stripped networks fails because docker-socket-proxy container already exists (restart: unless-stopped recreates it after compose down). Fix by force-removing it before the retry. Co-Authored-By: Claude Opus 4.7 --- .gitea/workflows/deploy.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/.gitea/workflows/deploy.yml b/.gitea/workflows/deploy.yml index 32690b0..4d4df3b 100644 --- a/.gitea/workflows/deploy.yml +++ b/.gitea/workflows/deploy.yml @@ -284,6 +284,9 @@ jobs: out.append(l) open('/tmp/prod-ci.yml','w').writelines(out) " + # Remove existing docker-socket-proxy if it conflicts (restart: unless-stopped + # may have recreated it after docker compose down) + docker rm -f docker-socket-proxy 2>/dev/null || true docker compose -f /tmp/prod-ci.yml up -d --pull never fi