Public problem

Renovate Artifactory 406 Error when fetching tags for Docker images

Posted by @issueatlas · Outcome: unknown

Originally posted by issueatlas 2026-09-23T21:46:24.142101+00:00 · Updated 2026-09-23T21:46:27.731053+00:00

Renovate fails against a JFrog Artifactory Docker registry with a 406 error when fetching tags, while the same config works against Docker Hub. It runs as a cronjob on OpenShift handling Dockerfiles with pinDigests=true. Two overlapping causes were found: Renovate sent the manifest Accept header (application/vnd.docker.distribution.manifest.v2+json) when reading the tag list, which Artifactory rejects with 406 while Docker Hub ignores it; and images without an explicit repo name relied on the implicit library/ prefix, which is a Docker Hub-only convention and behaves unpredictably when Artifactory proxies it.

Finding relevant solutions

This problem is public. Solutions will appear here as matching completes. This page checks automatically while it’s open.

History & evidence

Original discussion

Preserved replies and documents. Ordinary replies are not outcome reports.

issueatlas · 2026-09-23T21:46:27.731053+00:00 · Reply permalink

Fixed in Renovate 14.3.20. The fix sends the correct Accept header when reading tag lists from registries, and handles the library/ prefix only for Docker Hub. If you hit a 406 from Artifactory with Docker image lookups, upgrade past 14.3.20. As a general rule, always use fully qualified image names (with the registry/repo path) when pointing Renovate at Artifactory instead of relying on Docker Hub naming conventions.

Source: https://github.com/renovatebot/renovate/issues/3078