For building Bahmni Docker Images we have been using openjdk:8 as the base image. But now the official builds of openjdk has been deprecated and is not up-to-date with latest security patches.
Please look this for more info.
So we started analysing some of the distributions like temurin, corretto, ibmjava etc. On comparison amazoncorretto:8 seems to be better, since it gives the following advantages.
We may need to re-publish Bahmni performance metrics if we are changing the underlying JVM, and compare the two.
We should prioritise moving away from JDK8… to newer versions (i feel we can do that for all except possibly OpenELIS, which is anyways being dropped soon). Looks like even this support will end in 2024. So, we better prioritise Java upgrade soon!!
Hello @raff, Bahmni team is using openmrs/openmrs-distro-platform:2.5.7 as the base image to build bahmni/openmrs image. We would like to know about a few things.
Where is the CI for openmrs-distro-paltform image, is it built from Github Actions and pushed to dockerhub or from somewhere else ?
Is this the dockerfile that is used to build the image ?
openmrs-distro-platoform:2.5.7 still runs on Tomcat 7.0.94, which has already reached End-of-Life. on March 2021. Is there any plans to upgrade to Tomcat 8 ?
Hello @raff Good day. Do yo have any updates about the new openmrs images ? Can you please help with an estimated time on when the new images would be available on docker hub for use ?
@mohant it wasn’t a quick change as the base OS changed from debian to amazon linux. It required a number of changes in packages and a bit more testing. I’m expecting to be done next week.
Change to openmrs-core master has been pushed and is published as nightly on dockerhub already. I’m updating platform and refapp right now and soon after I’ll backport to openmrs-core 2.5.x and platform. I should be done in a few hours.
@mohant I need to wait with committing the changes to platform until 2.5.8 release is complete. openmrs-core 2.5.8 has been released with the old approach and there’s a pending 2.5.8 platform release. A good news is that openmrs-core 2.5.x-nightly image is available so you could start testing from that and switch to platform once ready. You can have a look at the platform master branch to get a feeling how to use it. Just replace dev and nightly with 2.5.x-dev and 2.5.x-nightly.
In general, for point-releases of core, I think we’ve only done a platform release if it’s specifically requested, i.e., not every release of core has necessarily meant we’ve needed a release of the platform…
@mohant the platform 2.5.x-nightly image is available on dockerhub. I’m planning to do a release of core and platform 2.5.9 on Tuesday next week so you can base your image on a released version.
Thanks @raff. We are planning to use openmrs-core:2.5.x-nightly and start testing.
By the way do you have any documentation on the environment variables that can be set? I could see there are number of variables possible in the startup script and some them seems to be different from existing environment variables.
@mohant I’ll update the docs before releasing. The startup-init.sh contains all supported variables. They are extracted to this one file to make it clear. The goal is to unify variables across all images: core, platform, refapp, o3.
Hello @raff. We have built bahmni/openmrs image based on openmrs-core:2.5.x-nightly image and it works both on Intel chip as well as M1 chip machines. Thanks for the fixes and refactoring. We will test it more in the upcoming days and let you know.
When can we expect the release of openmrs-core:2.5.9 so that we can base our image with a specific tagged release ?