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 <noreply@anthropic.com>
2026-05-23 23:35:53 +08:00
parent efaa0da5ed
commit a19b207043
1 changed files with 3 additions and 0 deletions
@@ -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