-
Notifications
You must be signed in to change notification settings - Fork 831
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use a more recent jdk base image #4815
Conversation
@@ -14,7 +14,7 @@ RUN gradle build --no-daemon --info | |||
################################################################################ | |||
|
|||
# Some dependencies require glibc, which Alpine does not provide | |||
FROM registry.access.redhat.com/ubi9/openjdk-17-runtime:1.14-2 | |||
FROM registry.access.redhat.com/ubi9/openjdk-17-runtime:1.14-2.1681917142 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
❓ Would latest
be preferable to the specific version?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We have not concluded yet whether it is alright to use latest
tag. So bumping up the version for now.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Shouldn't rebuild with 1.14-2
(if it is a rolling tag) basically include the latest version of it, in this example 1.14-2.1681917142
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
1.14-2
is not a rolling tag (1.14
is).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd probably stick to 1.14
then same way as I'd use for base ubuntu:22.04
and not specific build of it - but you are right we did not make specific decision on these yet.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We can look at changing to 1.14
in future; this is fine for now
What this PR does / why we need it:
Update
dataflow-engine
base jdk image to use a more recent one to sort out CVEs.At the time of writing:
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer: