Background: we are using the dockerized version of orthanc (orthanc-plugins) with docker compose.
There was already an 1.5.8 version of the image published 4 months ago. This meant that even though I bumped our image version,
since I already had a jodogne/orthanc-plugins:1.5.8 image locally on our machines, the new image wasn’t pulled and the old one was used instead.
I had to manually delete the old 1.5.8 image so docker could pull the new one.
I think a new docker tag should have been used for this new release, maybe it was a mistake?
Best,
András
Simply force the update of the images by typing:
$ docker pull jodogne/orthanc-plugins:1.5.8
Then, you’ll see the following in the logs:
$ docker run -p 4242:4242 -p 8042:8042 --rm jodogne/orthanc-plugins:1.5.8
W0307 10:11:23.422715 main.cpp:1524] Orthanc version: 1.5.8
[…]
W0307 10:11:23.647258 PluginsManager.cpp:269] Registering plugin ‘dicom-web’ (version 1.1)
The “jodogne/orthanc” and “jodogne/orthanc-plugins” image are focused on the release cycle of the Orthanc core. If you want more holistic versioning with more control over the plugins through environment variables, check out the “osimis/orthanc” images:
https://osimis.atlassian.net/wiki/spaces/OKB/pages/26738689/How+to+use+osimis+orthanc+Docker+images
HTH,
Sébastien-
NB: Contrarily to “jodogne/orthanc-plugins”, the “osimis/orthanc:latest” images do not embed version 1.1 of DICOMweb yet.