4.x: Update Dockerfiles to use jdk-no-fee-term instead of openjdk #8733
Conversation
This file contains 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
oracle-contributor-agreement
bot
added
the
OCA Verified
romain-grecourt
approved these changes
May 9, 2024
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.
Description
Update Dockerfiles to use
jdk-no-fee-termJDK instead ofopenjdk. Related to #5209. Reasons why:openjdkstops getting updates after the next version of the JDK is released.jdk-no-fee-termgets updates until one year after the next LTS version (so much longer)openjdkrepo, no login is needed. So user experience should not be impacted.Tip: if for some reason you run into authentication errors with
container-registry.oracle.com(even when accessing repositories that should not require authentication) it might be caused by cached expired credentials mucking up the works. Try this:Documentation
No change