renovatebot / renovatebot/github-action
Retry docker image pull on failure
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- TypeScript
- Stars
- 546
- Forks
- 115
- Avg merge
- 19h 4m
- Merged PRs (30d)
- 10
Description
Periodically we get a failed build because ghcr.io was a bit erratic. I suspect a retry of the pull with a few seconds delay would have worked.
e.g.
Unable to find image 'ghcr.io/renovatebot/renovate:39' locally
39: Pulling from renovatebot/renovate
docker: Get "https://ghcr.io/v2/renovatebot/renovate/manifests/sha256:c186f5db05148fa5fd0bba339c09012762c31138163ebac947e782546d5158b0": dial tcp 140.82.114.33:443: i/o timeout.
See 'docker run --help'.
Error: The process '/usr/bin/docker' failed with exit code 125
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the GitHub Action entry point that invokes Docker and reproduce the ghcr.io pull timeout shown in the issue. Trace the pull failure path and verify that a transient failure is retried after a delay, with the build still failing clearly when retries are exhausted.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, github-actions, typescript
- Domain
- ci-cd, devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100