How to get around GitLab's Registry Dependency Proxy limitation of not listing tags #36160
Unanswered
mhagnumdw
asked this question in
Request Help
Replies: 1 comment
-
use registry alias |
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
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 CE 17.5.0, renovatebot/renovate:40.19.2
Please tell us more about your question or problem
I've already researched a lot and I continue to research, somehow these discussions are related: #26847, #27917, #35833
In my repos that have
Dockerfile
that use GitLab's Dependency Proxy, eg:are not notified of
nginx
update. I tried removing the-alpine
suffix for testing and it works the same.I also get the warn in the Renovate configuration merge request:
After adding the below
customManagers
, I now receive updates fornginx:1.25.2-alpine
, but the above warn persists:The warn (see logs) must be because GitLab's dependency proxy does not support the
/tags/list
endpoint, see here.Since GitLab's dependency proxy downloads images from Docker Hub, would it be possible to configure Renovate to list images from Docker Hub? Would this count towards Docker Hub accesses?
Another thing: although
customManagers
solved part of my problem, I wonder if it is really necessary or if there is already another solution.Tks!
Logs (if relevant)
Logs
Beta Was this translation helpful? Give feedback.
All reactions