Docker datasource bypasses abortOnError: one transient Docker Hub EPIPE aborts the entire repository run (port #44326 to docker)

[lusoris]

Describe the proposed change(s).

abortOnError: false host rules have no effect on the docker datasource: lib/modules/datasource/docker/{common,index}.ts throws ExternalHostError directly on RequestError/429/5xx, and lib/workers/repository/error.ts then aborts the entire repository run unconditionally on any ExternalHostError.

Practical effect (observed on v43.281.1, self-hosted): a repository scan extracted 777 dependencies, hit a single transient RequestError: write EPIPE on GET https://index.docker.io/v2/ for one anonymous Docker Hub lookup, logged External host error causing abort - skipping, and finished "result": "external-host-error" after 855 s — discarding the whole 14-minute scan, including all pending helm lookups, because of one TCP reset on one unauthenticated endpoint. A scoped host rule (matchHost: "docker.io", abortOnError: false) was verified to be a no-op against the pinned source for exactly this reason.

#44326 (merged 2026-07-07) fixed this same class by replacing the direct throw with handleGenericErrors — but only for the repology datasource. This issue asks for the same treatment in the docker datasource, so abortOnError: false regains its documented meaning there. Related discussion of the bug class: #44329.

Happy to test a fix against our self-hosted setup — the failure reproduces multiple times per week at our scan volume.

[github-actions[bot]]

Hi there,
We notice that the Discussion you've created doesn't quite follow our template.
Please update the top-level comment in this Discussion to follow the structure of the template.
This improves the maintainers' time to triage, as key information is clearly indicated in the format we expect.
Thanks, the Renovate team