First of all, I highly appreciate the work of everyone involved in Orthanc and I am aware that is mostly volunteering work. I am not demanding anything here, I’d just like to share with you the problems I face and hope to get some input for a solution that can benefit others.
Our PACS stack is based on the jodogne/orthanc-python:1.10.1 docker image of Orthanc.The last fixed version (non-“latest”) available is still 1.11.0 even though it contains some bug that was fixed in 1.11.2 according to the changelog: https://hg.orthanc-server.com/orthanc/file/Orthanc-1.11.2/NEWS so I didn’t want to upgrade from 1.10.1 yet.
I’ve been waiting for an official 1.11.2 release but I started wondering if the osimis docker images took over this role and the images from jodogne (dockerhub) will no longer be released. Question #1: Is this the case?
Ideally I would not want to switch to the osimis images becase I do not need the extra plugins (even in the non-full version) and also want to avoid changing too much of our current, working configuration.
Yes, the Docker images “jodogne/orthanc” and “jodogne/orthanc-plugins” will soon be updated, but I cannot tell when, presumably in January 2023.
These images are used in the context of the scientific activities of my research lab at UCLouvain university, which requires maximal stability in Orthanc.
May I ask how you achieve “maximal stability”? Are there any known issues with 1.11.2 or you just want to do more manual testing and you need more time?
I’d also love to know how you do the official Orthanc releases. Is it manual or do you have some CI pipelines?
I’d like to offer my help, if I can, I’ve been doing infrastructure automation in AWS and Azure for the past years.
Also, what did you mean by involving your research team?
Speaking of the osimis/orthanc Docker images, we do have CI on Github and all integration tests are executed every night on the stable and unstable branches. If the page is quite red right now, that’s because of a build issue in the unstable branch but the stable builds are ok.
These integration tests are run with Docker but they also allow us to trust an Orthanc release like the 1.11.2. We are still running valgrind manually to look for memory leaks and this happens only after a major change or before an official release.
Speaking for my part, we don’t upgrade right now as we are currently conducting new research developments precisely on the top of 1.10.1. This is what I meant by “maximal stability”. I’ll upgrade the image when time, after the associated publications we are currently working on are submitted.
Besides the GitHub CI mentioned by Alain, note that the Orthanc project also runs an in-house CIS infrastructure that leverages BuildBot on virtual machines.
Finally, by “involving my research team”, I mean proposing to embed us in a research project, or to associate us in a scientific work.
Thanks a lot, Alain and Sébastien for the quick replies.
I’m thinking about switching to the Osimis images simply because those are updated much more frequently.
As far as I know, Orthanc (and the jodogne/orthanc… images) are free to be used in a business / for-profit setting, correct?
Is that also the case, for the Osimis images?
Note again that it is the single time in the history of Orthanc that “jodogne/orthanc” and “osimis/orthanc” are not synchronized. They are generally updated together. This de-synchronization shouldn’t happen in the future.
You can find information about the licensing of Orthanc in the Orthanc Book: