I’ve been working on moving our Docker mage to using Temurin and I think we are in a good
shape to make that move.
Henri-Laiho did the actual change in the PR
https://github.com/jboss-dockerfiles/wildfly/pull/161 and I’ve been updating the GitHub
action to be able to build multiarch (ARM & AMD) JDK 11 and 17 images from the
Dockerfile.
With that change, we will provide much requested features to our Docker images:
* JDK 17 support
* ARM architecture
* Updated JDK/OS versions
I’ve been testing it on my own container registry at
https://quay.io/repository/jmesnil/wildfly?tab=tags and the images looks good.
I can not test the ARM builds but the Intel ones work just fine.
If users with access to ARM machine could test them, that’d be great.
I am planning to publish all images under a single image registry
quay.io/wildfly/wildfly.
We would then append the idk version to the WildFly version in the image tag/ the
convention would be:
quay.io/wildfly/wildfly:<wildfly version>-jdk<jdk-version>
I’m not planning to publish the latest tag anymore if we provide multiple jdk versions.
Instead, there will be latest-<jdk-version> for each JDK version we want to
provide.
So, for the current WildFly 26.1.2.Final; we would have 4 tags:
quay.io/wildfly/wildfly:26.1.2.Final-jdk11
quay.io/wildfly/wildfly:latest-jdk11
quay.io/wildfly/wildfly:26.1.2.Final-jdk17
quay.io/wildfly/wildfly:latest-jdk17
Once we release WildFly 27.0.0.Final, we would publish images for it and the latest-jdkXX
will point to their respective 27.0.0.Final-jdkXX tags.
For users that relies on the existing quay.io/wildfly/wildfly:latest tag, they will have
to update their images to use latest-jdk11 to keep pulling the latest image of WildFly
running on JDK11.
I’m waiting for confirmation that the images I’ve built works fine and then we will be
able to do the changes and push the image to the official quay.io/wildfly/wildfly
container registry.
Best regards,
Jeff
--
Jeff Mesnil
Principal Software Engineer
Red Hat
http://jmesnil.net/