Change base image from jre-jammy to jre-noble for security improvements #229
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.
Hello,
We're using official Apache Flink Java images as base images in our project, but our security scans have identified numerous vulnerabilities originating from these base images. We want to continue using official images; however, to do so, we must address these security issues. It appears that the majority of vulnerabilities stem from Ubuntu 22, which is part of the jre-jammy base image. We propose switching to the jre-noble base image to migrate to Ubuntu 24, which contains the latest security fixes.
What Changed
generator.sh
to useeclipse-temurin:*-jre-noble
instead ofeclipse-temurin:*-jre-jammy
Why
Testing
Locally built and tested
flink:1.20.2-scala_2.12-java17-noble
successfully.Impact
This change will update the base image for ALL Flink Docker variants when the next Dockerfiles are generated.