Add corretto-al2023 variants
#305
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@yosifkit we expect to release Temurin 21 in the next 1-2 days |
|
@yosifkit you should be able to use Temurin now |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adding these to get a JDK that is version 21+ with OpenSSL 3.x available. This is mostly because OpenJDK 21 reached GA and so it was dropped from the
openjdkimages (docker-library/openjdk#531) and as such, we now don't have a base image for the Tomcat 11 alpha builds (836a850).Alternative is to wait for the eclipse-temurin JDK 21 images: adoptium/temurin#7, https://adoptium.net/blog/2023/09/temurin21-delay/.
This is subset of #299; perhaps it should be limited in some way?
Edit: 😢That's a lot of extra code because al2023 is not a drop in replacement for al2: a40c1c3