Skip to content

fix: avoid exiting when a registry rate limits or returns an unexpect… - #184

Open
fooltinkerer wants to merge 1 commit into
sergi0g:mainfrom
fooltinkerer:fix/rate-limit-crash
Open

fooltinkerer wants to merge 1 commit into
sergi0g:mainfrom
fooltinkerer:fix/rate-limit-crash

Conversation

@fooltinkerer

@fooltinkerer fooltinkerer commented Nov 6, 2026 •

Copy link
Copy Markdown
Contributor

A 429 from a registry hit the error! macro, which calls process::exit. In server mode the container then restarted and hit the same limit again on the startup check.

Failed requests now mark the affected images as Unknown with the reason
instead of exiting:

  • 429 gets its own warning, including Retry-After when the registry sends it
  • other unexpected statuses and network errors return an error
  • token and auth-challenge failures mark all images of that registry
  • a missing docker-content-digest header marks only that image

Closes #179

Feedback welcome so as to make this PR ready for a merge.

@fooltinkerer
fooltinkerer marked this pull request as ready for review November 6, 2026 14:55

This branch has not been deployed

No deployments
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.

[BUG] Registry 429 response causes fatal error leading to container restart loop

1 participant