Renovate authentication issue with docker hub #29213
Unanswered
robinschneider
asked this question in
Request Help
Replies: 2 comments
-
You are possibly getting rate limited even after using valid credentials - it's easy to do if you run often. You should try running with no hostRules, or with an intentionally wrong username, to compare the results. It's too early to make the conclusion that no token is used. |
Beta Was this translation helpful? Give feedback.
0 replies
-
you should enable redis cache, so renovate doesn't call to the registry on every run |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
What would you like help with?
I would like help with my configuration
How are you running Renovate?
Self-hosted
If you're self-hosting Renovate, tell us which platform (GitHub, GitLab, etc) and which version of Renovate.
GitHub
Please tell us more about your question or problem
We have a self hosten renovate running every 5 minutes. Most of our dependencies are internal and they change quite frequent and renovate is part of our ci/cd landscape, that's why we are required to run it that often.
However, some containers are in public docker hub.
We are getting rate limited because of the hight amount of renovate runs.
We are paying for docker hub to have a higher rate limit but renovate seems not to use the credentials provided.
Logs (if relevant)
Our configuration (running in Kubernetes with external secrets):
Our secret is there, I can use the username and password from the secret to do some
docker login
in my local terminal and it works just fine. REG01, REG02 and REG03 are self hosted registries and work just fine.Logs
Beta Was this translation helpful? Give feedback.
All reactions