Use Java 21 in Debian / Ubuntu images

[big-r81]

No description provided.

[nickva]

+1

[nickva]

@big-r81 I'll merge then try also update the Erlang 26 build and run buildx on all the images

[nickva]

This is failing the update to the latest OTP 25

> [linux/ppc64le internal] load metadata for docker.io/library/debian:bullseye:
------
debian-bullseye:22
--------------------
  20 |     ARG repository=debian
  21 |     
  22 | >>> FROM $repository:bullseye
  23 |     
  24 |     # Install Java
--------------------
ERROR: failed to solve: debian:bullseye: failed to resolve source metadata for docker.io/library/debian:bullseye: no match for platform in manifest: not found

Not all those debian/ubuntu versions have Java 21

[big-r81]

then we should use Java 17 in Debian Bullsye?

[nickva]

Maybe it just can't find bullseye altogether? [linux/ppc64le internal] load metadata for docker.io/library/debian:bullseye: that seems odd. Maybe an architecture specific things for PPC64LE

[big-r81]

or a temporary network / server error?

[big-r81]

oh there is now ppc64le bullseye image ...

[big-r81]

I remeber this from docker-library/official-images#17633 (comment)

From the CI:

Invalid 'FROM' + 'Architectures' combinations detected:

• couchdb:3.3.3 (FROM debian:bullseye-slim) [ppc64le, s390x]

Debian Bullseye is officially in LTS now, so the set of supported architectures is limited and you'll need to either drop the now-unsupported ones or update to Bookworm.

[nickva]

https://hub.docker.com/_/debian/tags?name=bullseye&ordering=-name

Huh, you're right, it is gone now.

https://www.debian.org/releases/bullseye/

The Debian 11 life cycle encompasses five years: the initial three years of full Debian support, until August 14th, 2024, and two years of Long Term Support (LTS), until August 31st, 2026. The set of supported architectures is limited during the Bullseye LTS term to i386, amd64, armhf and arm64. For more information, please refer to the Security Information webpage and the LTS section of the Debian Wiki.

Well this puts a monkey wrench in our release. I'll have to update the CI scripts and package scripts with exceptions for various version/arch combinations.

[nickva]

Here is my jumping through hoops patch to handle the issue: #77