Having Docker images in a local registry, but getting new versions from Docker Hub #21185
Unanswered
interN3rd
asked this question in
Request Help
Replies: 1 comment
-
|
Try setting a package rule with matchDatasources=docker and registryUrls=https://your-registry |
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
If you're self-hosting Renovate, tell us what version of Renovate you run.
35.x
If you're self-hosting Renovate, select which platform you are using.
Bitbucket Server
If you're self-hosting Renovate, tell us what version of the platform you run.
No response
Was this something which used to work for you, and then stopped?
I never saw this working
Wanted end result.
In the end, I want Renovate to scan the local Docker registry of my organization for current Docker images in use and I want Renovate to lookup new versions available in Docker Hub for it to then create a pull request.
Let's say, I have a Docker image in my organization's local repository and it's version
{Some_Docker_Image}:1.1.1. I then want Renovate to know about this Docker image and to lookup new versions of{Some_Docker_Image}:1.1.1in Docker Hub, to then create a pull request. Let's say,{Some_Docker_Image}:1.2.0is available in Docker Hub. I then want to configure Renovate in a way, that it know about this new version from Docker Hub and to create a pull request. This pull request would then be the notification to me, so I know that I have to update the local Docker registry.Is there any way to configure Renovate that way or am I trying to apply a wrong solution to an otherwise solvable problem?
What you tried so far.
Relevant debug logs
Logs
Beta Was this translation helpful? Give feedback.
All reactions