-
Notifications
You must be signed in to change notification settings - Fork 60
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
[OPENJDK-2411] JDK21 images for UBI8 #415
Conversation
This is/was used in order to let non-privileged scripts adjust the running user's GECOS field information, by re-directing lookups from /etc/passwd to $HOME/passwd. See OPENJDK-312. More modern container runtimes (e.g. CRI-O) now update the GECOS for the running user. Signed-off-by: Jonathan Dowland <[email protected]>
Define environment variables capturing the values for the user's name (USER), uid (UID) and user-name/comment/gecos (GECOS, see passwd(5)) in the jboss.container.user module. Replace hard-coded references to those values in scripts across all the other modules. For those modules which now use these variables, add an explicit dependency on jboss.container.user if it wasn't already present. The primary reason for this change is to reduce the delta between the ubi8 and ubi9 branches, which will avoid merge conflicts for future backports from ubi9 to ubi8. The secondary reason is to reduce the risk of a discrepancy for the values across the scripts. Signed-off-by: Jonathan Dowland <[email protected]>
Signed-off-by: Jonathan Dowland <[email protected]>
Signed-off-by: Jonathan Dowland <[email protected]>
Signed-off-by: Jonathan Dowland <[email protected]>
It is not useful to test for the mere presence of the 'release' label, since we inherit it from our base image. It's not especially helpful to check architecture=x86_64 either, which rules out running the test suit on any other architecture. Signed-off-by: Jonathan Dowland <[email protected]>
Don't test for 'release' or 'architecture' labels which we don't set in our image sources anyway. Check for strings in the values of the 'version' and 'name' labels, to be sure we've set them and not just inherited them. Split the label-check test into those which apply to all images, and those which are builder-only. Signed-off-by: Jonathan Dowland <[email protected]>
Signed-off-by: Jonathan Dowland <[email protected]>
Signed-off-by: Jonathan Dowland <[email protected]>
Signed-off-by: Jonathan Dowland <[email protected]>
Signed-off-by: Jonathan Dowland <[email protected]>
I am doing a round of scratch builds for these and running the behave test suite locally. |
all passed |
- name: jboss.container.openjdk.jdk | ||
version: "21" | ||
- name: jboss.container.maven | ||
version: "3.8.17" |
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.
3.8.21
?
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.
Good catch. At the moment there is no maven-openjdk21
RPM package, which would be what 3.8.21
should install (once the module exists), but we expect there to be in the future. So I think for now it's ok to use the 17 one in conjunction with singleton-jdk.
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.
OK.
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.
@jmtd is there a ticket to track the creation of maven-openjdk21?
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.
There is for RHEL 9.4 (RHEL-13046), but not (yet) for 8.10. I asked the filer of the former whether they'd like me to clone for the latter and haven't yet had a response.
Signed-off-by: Jonathan Dowland <[email protected]>
https://issues.redhat.com/browse/OPENJDK-2411