feat(build): use chainguard jre:latest-dev base image for docker healthcheck support #882
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
tronghn
force-pushed
the
chainguard-jre-healthcheck
branch
from
f297717 to
a3a198c
Compare
tronghn
force-pushed
the
chainguard-jre-healthcheck
branch
from
a3a198c to
eebe561
Compare
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.
Resolves #784, supersedes #811.
The
latest-devtag adds some utilities such aswgetto the runtime environment, allowing us to continue using jib and not having to maintain a separate base image that would addcurl.However, we do have to use the
latesttags for the JRE here, which currently uses targets JRE 24 (and soon 25). I don't think it'll cause any issues, but it's something to be aware of.