Update base image to OpenJDK 26-ea-17-jdk-slim#2
Update base image to OpenJDK 26-ea-17-jdk-slim#2mo-jasim wants to merge 1 commit intoLondheShubham153:masterfrom
Conversation
WalkthroughThe Dockerfile base image was updated from Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes
Poem
Pre-merge checks and finishing touches✅ Passed checks (3 passed)
✨ Finishing touches🧪 Generate unit tests (beta)
Tip 📝 Customizable high-level summaries are now available in beta!You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.
Example instruction:
Note: This feature is currently in beta for Pro-tier users, and pricing will be announced later. Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
| # Use the official OpenJDK 17 image as the base image | ||
| FROM openjdk:17-jdk-alpine | ||
| FROM openjdk:26-ea-17-jdk-slim |
There was a problem hiding this comment.
Update the comment to reflect the actual Java version.
The openjdk image has been deprecated, so the old image reference is understandable. However, the comment on line 1 still refers to "OpenJDK 17," but the FROM statement uses a Java 26 EA image. This creates a maintenance concern.
Update the comment to match the actual image:
-# Use the official OpenJDK 17 image as the base image
-FROM openjdk:26-ea-17-jdk-slim
+# Use the official OpenJDK 26 (Early Access) image as the base image
+FROM openjdk:26-ea-17-jdk-slim📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| # Use the official OpenJDK 17 image as the base image | |
| FROM openjdk:17-jdk-alpine | |
| FROM openjdk:26-ea-17-jdk-slim | |
| # Use the official OpenJDK 26 (Early Access) image as the base image | |
| FROM openjdk:26-ea-17-jdk-slim |
🤖 Prompt for AI Agents
In Dockerfile around lines 1 to 2, the comment incorrectly states "OpenJDK 17"
while the FROM line uses openjdk:26-ea-17-jdk-slim; update the comment to
accurately reflect the actual base image and Java version (e.g., mention OpenJDK
26 EA or the specific image tag used) so the comment matches the FROM line and
avoids future confusion.
| @@ -1,5 +1,5 @@ | |||
| # Use the official OpenJDK 17 image as the base image | |||
| FROM openjdk:17-jdk-alpine | |||
| FROM openjdk:26-ea-17-jdk-slim | |||
There was a problem hiding this comment.
🧩 Analysis chain
Verify the base image tag and consider stability/production readiness.
The openjdk image tags include pre-release / non-production builds of OpenJDK. Upgrading from the stable Java 17 LTS image to a Java 26 Early Access image introduces several risks:
- EA builds are not production-ready: Java 26 EA may contain breaking changes and instability.
- Significant version jump (17 → 26): Verify the application has been tested against Java 26 EA.
- OS change (Alpine → Debian): The base OS has changed from Alpine Linux to Debian slim, affecting image size and dependencies.
- Tag uncertainty: The tag format
26-ea-17-jdk-slimis atypical—verify this tag is correct and not a misprint (e.g., should it be26-ea-jdk-slim?).
Before merging, please:
- Confirm the tag
26-ea-17-jdk-slimexists and is correct. - Verify the application has been tested against Java 26 EA.
- Justify the need for Java 26 EA over stable LTS versions (Java 17, 21, etc.).
- Consider reverting to a stable LTS image (e.g.,
openjdk:17-jdk-slimoropenjdk:21-jdk-slim) unless Java 26 EA is explicitly required.
If production stability is a concern, consider using Eclipse Temurin (formerly AdoptOpenJDK) as an alternative.
---
🌐 Web query:
```web
Java 26 release date EA status 2025
💡 Result:
Short answer — status as of late 2025:
- JDK 26 is in active Early-Access (EA) with multiple EA builds available (JDK 26 and JavaFX 26 EA builds). [1][2]
- Oracle/Mark Reinhold proposed the official JDK 26 release schedule: rampdown starts Dec 4, 2025; Initial RC Feb 5, 2026; GA (general availability) targeted Mar 17, 2026. [3]
Sources:
- JavaFX 26 EA builds page (notes that JDK 26 EA is recommended). [jdk.java.net/javafx26]. [1]
- OpenJDK/project updates mentioning JDK 26 EA and JavaFX 26 builds. [openjdk / project announcements]. [2]
- InfoQ summary of the proposed JDK 26 release schedule (dates above). [3]
🌐 Web query:
openjdk 26-ea jdk-slim docker tag format
💡 Result:
Tag format (pattern)
- -ea(-)?-jdk-slim(-)?
Common examples
- 26-ea-24-jdk-slim-bookworm. [1]
- 26-ea-23-jdk-slim-trixie. [2]
- 26-ea-20-jdk-slim-trixie. [2]
- 26-slim (stable non-ea variant). [3]
Meaning
- 26: Java major version.
- ea: early-access (pre-release).
- 24 / 23 / 20: build/iteration number.
- jdk-slim: full JDK image using a slim base.
- bookworm / trixie: base OS / distro variant (optional).
Sources: Snyk tag listings for openjdk images and Docker Hub mirror listing. [1][2][3]
🌐 Web query:
Java 26 production ready stable release
💡 Result:
Short answer: Not yet — JDK 26 is still in development/EA and its planned General Availability (GA) is March 17, 2026. Wait for the GA release before using it as a production/stable runtime; continue using your current supported JDK (or the latest vendor GA/LTS) until then. [1][2][3]
Sources:
- OpenJDK JDK 26 project page (status & schedule). [1]
- JDK-Dev announcement with the proposed JDK 26 schedule (GA = 2026-03-17). [2]
- JDK 26 early-access release notes (EA builds available for testing). [3]
Fix the Docker base image tag format and address Java 26 EA production readiness.
The tag openjdk:26-ea-17-jdk-slim is malformed and refers to a pre-release that is unsuitable for production:
- Tag format is incorrect: The correct format is
26-ea-<build_number>-jdk-slim(e.g.,26-ea-24-jdk-slim-bookworm). The17in your tag occupies the build number position and appears to be confusion with the previous Java 17 version. - Java 26 is not production-ready: Java 26 Early Access is still under development with General Availability (GA) targeted for March 17, 2026. This is not suitable for production deployments.
- Significant version and OS changes: Upgrading from Java 17 LTS (Alpine) to Java 26 EA (Debian-based) is a major change that requires thorough testing.
Fix the Dockerfile before merging:
- Correct the tag to a valid Early Access build if Java 26 EA is explicitly required (e.g.,
openjdk:26-ea-24-jdk-slim-bookworm), or - Revert to a stable LTS image (e.g.,
openjdk:21-jdk-slim) for production stability.
Verify the application has been tested against the chosen Java version.
🤖 Prompt for AI Agents
In Dockerfile around line 2, the base image tag openjdk:26-ea-17-jdk-slim is
malformed and points to an Early Access Java 26 build that is unsuitable for
production; fix it by either replacing the tag with a valid EA build (e.g.,
openjdk:26-ea-24-jdk-slim-bookworm) if you intentionally require Java 26 EA, or
preferably revert to a stable LTS image such as openjdk:21-jdk-slim for
production; after changing the tag, run your test suite and smoke tests to
verify the application behaves correctly on the chosen Java version before
merging.
1 participant
Old openjdk:17-jdk-alpine Was expired so I have added new one: openjdk:26-ea-17-jdk-slim
Summary by CodeRabbit
✏️ Tip: You can customize this high-level summary in your review settings.