mirror of
https://github.com/NousResearch/hermes-agent.git
synced 2026-07-30 19:09:28 +00:00
acfd376d66
The Docker Build, Test, and Publish workflow fails when docker/setup-buildx-action can't pull the moby/buildkit:buildx-stable-1 image from Docker Hub. The failure happens during builder bootstrap at the auth token exchange — a transient network blip (connection reset, read timeout, rate limiting) that self-resolves on re-run. Recent failure (run 30449230291, merge job): read tcp 10.1.0.171:45666->104.18.43.178:443: read: connection reset by peer This has hit us before and will again — it's the same class of transient Docker Hub flake that the merge job already retries for imagetools create. But buildx setup had no retry, so a single network hiccup killed the entire job (build, publish, or merge) even though nothing was wrong with the code or the image. Fix: wrap each of the 3 buildx setup steps (build, publish, merge jobs) with continue-on-error + a conditional retry step. The maintained action is preserved as-is — we just give it a second attempt if the first fails. The action generates a unique builder name per invocation, so the retry never collides with the failed first attempt. The second attempt has no continue-on-error, so genuine persistent failures still fail the job. The docker/setup-buildx-action maintainer has explicitly said retry belongs at the workflow level, not inside the action [1], and other repos use this same continue-on-error pattern for this exact issue [2]. [1] docker/setup-buildx-action#510 [2] joshjhall/containers#688, ethpandaops/eth-client-docker-image-builder#391 |
||
|---|---|---|
| .. | ||
| actions | ||
| ISSUE_TEMPLATE | ||
| pr-screenshots | ||
| workflows | ||
| dependabot.yml | ||
| PULL_REQUEST_TEMPLATE.md | ||