RegistryAliases and registryUrls not working for ECR cache setup #38673
Replies: 3 comments
-
|
Is there any chance to get help on that? Is it a bug or configuration issue? :( |
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.
-
|
Related: #41500 |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
How are you running Renovate?
Self-hosted Renovate
If you're self-hosting Renovate, tell us which platform (GitHub, GitLab, etc) and which version of Renovate.
GitLab
Please tell us more about your question or problem
Hi!
I'm running ECR pull through cache and I cache a lot of dockerhub images.
I want to use Renovate to lookup in dockerhub for the latest images tags but still use ECR URLs.
Here is my setup, after many trials/chatgpt'ing/docs research:
At this moment, this is how the Dockerfile looks like..
I tried with
registryUrlsalone,registryUrlswith morematch*conditions insidepackageRules, triedregistryAliases, different values forregistryUrls, with regexes and just strings... everything that came to my mind.Looks like Renovate is ignoring these parameters, for EVERY run I'm getting following result:
Logs (if relevant)
No response
Beta Was this translation helpful? Give feedback.
All reactions