Checking a public container registry for mirrored, private images #37022
Replies: 2 comments
-
|
Try |
Beta Was this translation helpful? Give feedback.
-
|
Hey, I ran into this same problem recently with Renovate pulling from Docker Hub and hitting rate limits all the time — super frustrating in CI. What worked for me was switching Renovate to use a public Docker mirror: Just add this to your renovate.json: { Hope it helps someone! |
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.
GitHub, Renovate 41.28.0
Please tell us more about your question or problem
I have several YAML files (Helm values) with registry, tag, etc. as values. Our company's policies force us to mirror/upload public images into our private registry for security scanning and to make it so our compute can't just pull random stuff from the internet.
The issue with this pull-through method is that the private registry only has whatever version we currently run for an app, or the previous. Ergo, renovatebot will never find a newer version in this registry.
Examples:
How could I make renovatebot parse these blocks of config (some charts put everything in
image:, others split it out intag:andregistry:) and look at Docker Hub, Quay.io or GHCR registries instead?Logs (if relevant)
Logs
Beta Was this translation helpful? Give feedback.
All reactions