Renovate removes digest from docker image after mutex timeout #30924
Unanswered
mvitz
asked this question in
Request Help
Replies: 2 comments 6 replies
-
Hi, please format any copy/pasted code or logs so they're readable. You can find a Markdown code formatting guide here as well as some GitHub-specific information formatting code blocks here. Thanks, the Renovate team |
Beta Was this translation helpful? Give feedback.
0 replies
-
Please split the log by \n and also ideally include more logs, including a good run and the bad run. Also clarify what exactly did renovate do. Eg create a new PR to remove digest or update an existing one, etc |
Beta Was this translation helpful? Give feedback.
6 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 think I found a bug
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.
GitLab, Renovate version 38.44.3
Please tell us more about your question or problem
Today there were a few runs where Renovate opened a MR for removing the digest of Docker images.
Because in my setting, digest updates are set to auto-merge, these were even merged.
Looking at the logs (see below for INFO, and attachment for a full DEBUG log) it contains ERROR entries for several Docker image updates with a mutex timeout.
I would expect that in case of such a failure, renovate would skip any actions and not remove the digest.
What looks a bit suspicious is that the regex manager detected 3076 dependencies, which is far too much. The attached DEBUG log shows that the it's a result of finding the same packages over and over. This packages are found by
"regexManagers:dockerfileVersions"
which is included via a preset.Logs (if relevant)
Logs
Beta Was this translation helpful? Give feedback.
All reactions