Image registry proxy/pull through cache strip additional prefix(es) #34610
Replies: 2 comments 2 replies
-
Have you tried |
Beta Was this translation helpful? Give feedback.
-
Hi there, Please help this Discussion progress by creating a minimal reproduction. This means a repository dedicated to reproducing this issue with the minimal dependencies and config possible. Before we start working on your issue we need to know exactly what's causing the current behavior. A minimal reproduction helps us with this. Discussions without reproductions are less likely to be converted to Issues. Please follow these steps:
If you need help with running renovate on your minimal reproduction repository, please refer to our Running Renovate guide. The Renovate team |
Beta Was this translation helpful? Give feedback.
-
Tell us more.
Split from #18112 (comment)
For example, ECR has the concept of pull through rules (Sync an upstream registry with an Amazon ECR private registry) similar to Harbor's proxy cache. The path has a prefix that indicates which remote to retrieve the image from so:
is retrieved from
This has many advantages like avoiding ratelimits. When running Renovate on these repositories the Dockerfile manager looks for new versions in
aws_account_id.dkr.ecr.region.amazonaws.com/ghcr/renovatebot/renovate
and not in the remote that it is set up to mirror leading to new versions not being detected properly.Suggested solution: there is already a list of hardcoded prefixes it would be great if we can configure this dynamically, so that renovate strips the prefix when looking for version on the remote.
Beta Was this translation helpful? Give feedback.
All reactions