maven:*-amazoncorretto-*debian rebuilds are failing

[yosifkit]

The rebuilds triggered by docker-library/official-images#18261 have run into a checksum failure on the corretto.key:

#13 7.748 sha256sum: WARNING: 1 computed checksum did NOT match
#13 7.748 corretto.key: FAILED

It looks like the key fila was also updated, so the relevant Dockerfiles just need to be updated with the new checksum. I am happy to make a PR if that'd be helpful.

root@77240abd2dab:/# curl -f -I https://apt.corretto.aws/corretto.key
HTTP/1.1 200 OK
Content-Type: binary/octet-stream
Content-Length: 2459
Connection: keep-alive
Last-Modified: Wed, 22 Jan 2025 21:38:17 GMT
x-amz-server-side-encryption: AES256
x-amz-version-id: L9gzcGMO6WM.BgUyuFyzbK4eMHd0eps_
Accept-Ranges: bytes
Server: AmazonS3
Date: Thu, 23 Jan 2025 21:39:56 GMT
ETag: "513fa3f9a3860ad43fac76097bb2fd9e"
X-Cache: Hit from cloudfront
Via: 1.1 d59d2ab357c0c409dc4be130a9aab01e.cloudfront.net (CloudFront)
X-Amz-Cf-Pop: LAX53-P4
X-Amz-Cf-Id: m9MLYhdil4xyD9H9ZmZJBV42ur4p_DH9ZySr55wTKkenKHUnI7FswA==
Age: 78757
root@77240abd2dab:/# curl -fsL https://apt.corretto.aws/corretto.key | sha256sum
5fdaed0a262b975776b1d5c0170d2e86b1be1e98b27ef97114b04ec9ac7f011d  -

[carlossg]

I'm thinking about removing the key file checksum as it was only there to force the image rebuild and use some other way.
Would having the Sha of the parent image FROM work for official images? And update it with Renovate

[carlossg]

Looks like having

FROM debian:bookworm-slim@sha256:f70dc8d6a8b6a06824c92471a1a258030836b26b043881358b967bf73de7c5ab

fails with stackbrew

changed the sha in #528 but looking for better ways