Introduce Java 21 #376
Comments
edeandrea
added
fights-service
|
@cescoffier With this we will publish both a JVM Java 17 & 21 container image for each app. Should we do the same with native? Or just a "latest" native (Java 21)? When we were doing both Java 11 & 17 we did both for JVM images but only did a 17 native. I'm thinking we continue with this pattern. Thoughts? |
|
At the moment, we can’t really use java 21 in native as we do not have the
mandrel 21 yet.
So I would keep java 17 for native.
…On Fri 6 Oct 2023 at 18:05, Eric Deandrea ***@***.***> wrote:
@cescoffier <https://github.com/cescoffier> With this we will publish
both a JVM Java 17 & 21 container image for each app. Should we do the same
with native? Or just a "latest" native (Java 21)?
When we were doing both Java 11 & 17 we did both for JVM images but only
did a 17 native. I'm thinking we continue with this pattern.
Thoughts?
—
Reply to this email directly, view it on GitHub
<#376 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AADCG7OUWLOZXWJGSMMOF23X6AT4ZAVCNFSM6AAAAAA5WAEZ66VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONJRGAYDIMJYGM>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
Well for now for native I would switch to use |
|
You can, it’s what I recommend. However we are not done with all the
testing. In other words, use it are your own risks 🤪
…On Fri 6 Oct 2023 at 19:02, Eric Deandrea ***@***.***> wrote:
Well for now for native I would switch to use
quay.io/quarkus/ubi-quarkus-graalvmce-builder-image
—
Reply to this email directly, view it on GitHub
<#376 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AADCG7OJNA7YJQSBJ3TT76TX6A2T7AVCNFSM6AAAAAA5WAEZ66VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONJRGEYTMMBYGQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
Right. I get that. What about building a container image for jvm on 21? There is no openjdk-21 image on registry.access.redhat.com. For now maybe I'll try to build my own on ubi-minimal. |
|
Yes, we do not have a ubi jdk 21 yet (waiting for a temurin 21 image).
…On Fri 6 Oct 2023 at 19:12, Eric Deandrea ***@***.***> wrote:
Right. I get that.
What about building a container image for jvm on 21? There is no
openjdk-21 image on registry.access.redhat.com. For now maybe I'll try to
build my own on ubi-minimal.
—
Reply to this email directly, view it on GitHub
<#376 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AADCG7OSLJRF36KQCHLHPLDX6A3YLAVCNFSM6AAAAAA5WAEZ66VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONJRGEZDSOBTGA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
This is what I'm going with for now... FROM azul/zulu-openjdk:21-jre
RUN mkdir -p /deployments/lib && \
mkdir -p /deployments/app && \
mkdir -p /deployments/quarkus
ENV LANG='en_US.UTF-8' LANGUAGE='en_US:en'
# We make four distinct layers so if there are application changes the library layers can be re-used
COPY target/quarkus-app/lib/ /deployments/lib/
COPY target/quarkus-app/*.jar /deployments/
COPY target/quarkus-app/app/ /deployments/app/
COPY target/quarkus-app/quarkus/ /deployments/quarkus/
EXPOSE 8087
ENTRYPOINT ["java", "-jar", "/deployments/quarkus-run.jar", "-Dquarkus.http.host=0.0.0.0", "-Djava.util.logging.manager=org.jboss.logmanager.LogManager"] |
|
Hey @cescoffier now that https://catalog.redhat.com/software/containers/ubi9/openjdk-21-runtime/6501ce769a0d86945c422d5f, Or should we have deployments for both 17 & 21, like we used to do for 11 & 17. We would only use 21 for native - I'm thinking just on the JVM side. I'm almost to the point of saying forget about 17, just go fully to 21. @holly-cummins / @agoncal / @cescoffier WDYT? |
Now that Java 21 is out, run all of the automation & produce Java 17 & 21 images for all the apps.
One note is that the Mandrel builder image doesn't yet have a Java 21 image, so for now we'll have to use the GraalVM CE builder image
The text was updated successfully, but these errors were encountered: