"Extraction digest from manifest response body is deprecated" message for single arch container images #28970
Replies: 2 comments 4 replies
-
The image {
"schemaVersion": 2,
"mediaType": "application/vnd.docker.distribution.manifest.v2+json",
"config": {
"mediaType": "application/vnd.docker.container.image.v1+json",
"size": 2877,
"digest": "sha256:2e911da29f8117119473a232cf4cd945802a730a98c32403bca702961139c20b"
},
"layers": [
...
]
} And per https://distribution.github.io/distribution/spec/manifest-v2-2/, type |
Beta Was this translation helpful? Give feedback.
4 replies
Answer selected by
aarongoldenthal
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
What would you like help with?
Other
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
Please tell us more about your question or problem
I was digging through a debug log today looking a separate issue and noticed a large number of container images reporting a "Extraction digest from manifest response body is deprecated" message in the logs. The images, and associated updates, are processed correctly, but mostly trying to understand the issue.
At first it appeared to be all of my images, which are all single arch amd64 images, built with the latest version of Kaniko (different versions over many months, but the
gcr.io/kaniko-project/executor:debug
image with default settings), and maintained in a GitLab container registry (several built today). But, closer review shows some of GitLab''s images, Microsoft's PowerShell image, a few images on Docker hub, etc. It's not every image referenced in that repository, but appears to be all of the single arch images.It appears this PR added the message, previously it was silently processed, but it didn't have an explanation for the deprecation (or whether it's actually a concern).
Logs (if relevant)
Logs
Beta Was this translation helpful? Give feedback.
All reactions