feat: migrate base image to RHEL9 (UBI9) for improved glibc support a… #281
+113
−48
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
…nd CVE transparency
|
|
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.
feat(docker): add RHEL9 (UBI9) base image variant for enterprise compatibility
What was changed
Added support for RHEL9 (UBI9) as an alternate base image in Dockerfile.
Why?
This enables easier adoption in enterprise environments that:
Checklist
Closes [Feature Request] Add support for RHEL9-based Docker images #280
How was this tested:
-Ran schema setup and migrations via temporal-sql-tool
-Verified temporal operator cluster health returns SERVING
-Ran docker-compose with UBI9-based images
-Confirmed port 7233 was reachable and workflows launched
-Validated setup with scripts/test.sh
Yes – if accepted, a note in the README.md mentioning UBI9 as an alternate base image option would help users in enterprise environments. No changes needed for docs.temporal.io at this point.