Skip to content

Retry flaky Docker registry push during release publish - #49

Draft
devops-rob wants to merge 1 commit into
mainfrom
cursor/fix-dockerhub-publish-retry-dea2
Draft

Retry flaky Docker registry push during release publish#49
devops-rob wants to merge 1 commit into
mainfrom
cursor/fix-dockerhub-publish-retry-dea2

Conversation

@devops-rob

Copy link
Copy Markdown
Contributor

Summary

Release publish failed on a transient Docker Hub timeout, not a credentials or image problem:

Published docker.io/nomatronio/derrick:0.11.4
Created manifest list docker.io/nomatronio/derrick:latest
failed to put manifest .../latest: Get "https://auth.docker.io/token?...": net/http: request canceled (Client.Timeout exceeded while awaiting headers)

The versioned tag (0.11.4) and manifest were published successfully; only the :latest manifest push failed while re-authenticating with Docker Hub.

Fix

Add exponential backoff retries (default 5 attempts, 4s initial delay) around docker push and docker manifest push in .github/scripts/publish_docker_registries.sh.

Change Classification

  • Open-core MPL files only (derrick)
  • New public files only (no MPL-covered modifications)

Test Plan

  • Script change only; will be exercised on next build workflow run on main.
  • Re-running the failed workflow may also succeed without this change, but retries make publish resilient to Docker Hub auth flakiness.
Open in Web Open in Cursor 

Docker Hub manifest push for :latest failed with a transient auth.docker.io
timeout after the versioned tag had already been published. Add exponential
backoff retries around docker push and docker manifest push.

Co-authored-by: DevOps Rob <devops-rob@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants