I understand! this is my sysadmin message:
"if nothing else, they could publish a new elasticsearch image of 7.6.2 (ex. 7.6.2-1) which uses a newer patched version of JDK (1.13.x but newer than 1.13.0_2)"
hi SuccessfulKoala55 ! has the docker compose been updated with this?>
In fact I just did that yesterday. I'll let you know how it goes
Well, it's a possibility but I'd rather work with official images. What's the closest image that satisfied this condition?
If you see anything out of the ordinary - let us know 🙂
Hi SuccessfulKoala55 , do you have an update on this?
"this means the elasticsearch feature set remains the same. and JDK versions are usually drop-in replacements when on the same feature level (ex. 1.13.0_2 can be replaced by 1.13.2)"
We're just now testing the latest ES docker, and it seems fine. I'll probably update the docker compose in the coming days. You can safely do it locally in your own docker-compose if you'd like
Hi ElegantCoyote26 ,
We're indeed planning to move to the newest version. It's always a delicate balance since sometimes upgraded versions require data migrations and/or code changes...
Hi ElegantCoyote26 , not yet - we've been a little busy with the Free Hosted ClearML 🙂 Did you try using the latest ES docker in your own deployment meanwhile?
hi SuccessfulKoala55 with the clearml server update, does it use a newer ES docker?