How do I handle docker tags with SHA1 hashes at the end?

[rcdailey]

How are you running Renovate?

A Mend.io-hosted app

If you're self-hosting Renovate, tell us which platform (GitHub, GitLab, etc) and which version of Renovate.

No response

Please tell us more about your question or problem

One particular docker image has tags that look like this:

• release-1.41.1.9057-af5eaea7a
• release-1.40.2.8395-c67dce28e

I'm not able to figure out how to tell Renovate to process these versions. I have the following in my renovate.json5:

    {
      // hotio tags use a format like "release-4.0.4.1491"
      // See: https://github.com/renovatebot/renovate/issues/7297
      //
      // Examples:
      // - release-1.40.2.8395-c67dce28e
      // - main-v1.52.8
      // - release-4.3.3
      "matchDatasources": ["docker"],
      "matchPackagePrefixes": [
        "ghcr.io/hotio/",
        "ghcr.io/berriai/"
      ],
      "versionCompatibility": "^(?<compatibility>[^-]+)-v?(?<version>.+)"
    },

In this case, when set at version release-1.41.1.9057-af5eaea7a, I do not get any upgrade PRs. The logs haven't been helpful in debugging the issue, but I feel like it's the -af5eaea7a at the end. I also tried loose versioning but I get wildly inaccurate upgrade PRs when I do that.

What am I missing?

Logs (if relevant)

No response

[bholland-bh]

https://docs.renovatebot.com/modules/versioning/loose/

{
  "$schema": "https://docs.renovatebot.com/renovate-schema.json",
  "packageRules": [
    {
      "matchDatasources": ["docker"],
      "matchPackagePrefixes": ["ghcr.io/hotio/", "ghcr.io/berriai/"],
      "versioning": "loose"
    }
  ]
}

[rcdailey]

I did this but with the version compatibility still in, and got some wildly inaccurate PRs.

I've already seen the linked page but there's no examples. No detailed explanation about the "loose" algorithm explaining how it works.

[rcdailey]

Looks like this solution doesn't work. Logs here

[rcdailey]

@rarkins I noticed you upvoted this answer, however it isn't working. I linked logs above. Sorry to ping you directly, but could you offer different advice? I'm stuck on this issue, despite my best effort to parse out the solution from the docs.

[rarkins]

Use versionCompatibility to separate the release- prefix from the version, then use loose versioning

[rcdailey]

Use versionCompatibility to separate the release- prefix from the version, then use loose versioning

@rarkins Here's what I tried (full json is here):

    {
      // Examples:
      // - main-v1.52.8
      // - release-4.3.3
      "matchDatasources": ["docker"],
      "matchPackagePrefixes": [
        "ghcr.io/hotio/",
        "ghcr.io/berriai/"
      ],
      "versionCompatibility": "^(?<compatibility>[^-]+)-v?(?<version>[\\d.]+)",
    },
    {
      // Example: release-1.40.2.8395-c67dce28e
      "matchPackagePrefixes": ["ghcr.io/hotio/plex"],
      "versioning": "loose"
    },

Logs are here and this is the resulting PR I get:

The next version should be release-1.41.2.9200-c6bbc1b53, taken from here.

What am I doing wrong?

[github-actions[bot]]

Hi there,

Get your discussion fixed faster 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:

1. Read our guide on creating a minimal reproduction.
2. Go to our minimal reproduction template repository.
3. Select the Use this template button to create a new repository based on the template.
4. Work on the minimal reproduction in your own repository.
5. Fill out the information in your repository's README.md.
6. Add the link to your reproduction to the first post of your Discussion. If you are not the original author, you can post a new comment with the link.

If you need help with running renovate on your minimal reproduction repository, please refer to our Running Renovate guide.
Good luck,

The Renovate team

[rcdailey]

@rarkins I'm not sure if you kicked this off as a response to my last comment, or if this was automated, but either way, I created a minimal reproduction here.

Interestingly, I get two PRs for the same thing, and not sure why. But either way, both PRs are wrong.

[github-actions[bot]]

Hi there,

We appreciate the effort you put into creating a reproduction. But your reproduction is not minimal yet, or is missing fields we ask for in our template.

Please re-read the steps and documentation given in the previous message, and try again to create a minimal reproduction.

Thanks, the Renovate team

[rcdailey]

After a lot of struggle, I managed to find out the answer on my own. The key is to make the versionCompatibility regex more comprehensive. Many tags for these particular docker images do not follow semver structure (e.g. large numbers with no dots in them), so those were being treated as upgrades instead, which was wrong.

The below package rule works well for my use case.

    {
      // hotio tags use a format like "release-4.0.4.1491"
      // See: https://github.com/renovatebot/renovate/issues/7297
      //
      // Examples:
      // - main-v1.52.8
      // - release-4.3.3
      // - release-1.40.2.8395-c67dce28e
      "matchDatasources": ["docker"],
      "matchPackageNames": [
        "/^ghcr.io/hotio//",
        "/^ghcr.io/berriai//",
      ],
      "versionCompatibility": "(?<compatibility>[^-]+)-v?(?<version>\\d+\\.\\d+\\.\\d+(?:\\.[\\w\\d.-]+)?)",
      "versioning": "loose",
    },