-
Notifications
You must be signed in to change notification settings - Fork 123
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
Create Dockerfiles for Liberty with UBI 9 minimal #666
Comments
@leochr have you discussed testing of the UBI 9 images with SVT? I think we will need InstantOn to be tested on these? |
@tjwatson Not yet. Trying to work out the dates with the build team on when the images would be available. @mtamboli FYI Liberty images with Java 21 are UBI 9 minimal based. Do you know whether InstantOn was tested on those images? Trying to assess whether this would be a validation for the other Java versions or validation on UBI 9 for the very first time. |
Yes, SVT has tested Java 21 with UBI 9 minimal. Are the UBI 8 images still going to exist? We will need some testing at least of each image. Not sure if we ever got automated tests enabled for our image builds? |
@tjwatson Thank you for confirming. I agree, as UBI 9 minimal-based Liberty was already tested with Java 21, some testing for the new images would suffice. UBI 8-based images will continue to exist (at least for now). The container automated test work was put on hold due to the migration to SPS (new pipeline) as the integration with the pipeline will need to be worked out. The new UBI 9 minimal-based images are expected to be available with the GM of 25.0.0.4 (April 8, 2025). @mtamboli please add the testing of the new images to the SVT plan/board. Thank you. |
Create Dockerfiles for Liberty with UBI 9 minimal and Semeu 8, 11 & 17 and IBM Java 8 (Note: existing Liberty images with Semeru 21 are already based on UBI 9 minimal).
Build locally and run the test/sample apps to validate. The CD/CC Build team will make the changes to the build repo to automate the building of these images as part of the OnePipeline.
The text was updated successfully, but these errors were encountered: