No persistent saving to docker volumes - jodogne/orthanc-plugins:1.12.4

General
1

I started from a working docker compose file from a official sample. Volume data was persistent accross docker compose down and subsequent docker compose up --build -d runs:

version: "2"
services:
  orthanc-pacs:
    build: orthanc-pacs
    restart: unless-stopped
    ports: ["8042:8042"]
    volumes: ["orthanc-storage-pacs:/var/lib/orthanc/db:Z"]
  orthanc-middleman:
    build: orthanc-middleman
    restart: unless-stopped
    ports: ["8043:8042"]
    volumes: ["orthanc-storage-middleman:/var/lib/orthanc/db:Z"]
  orthanc-modality:
    build: orthanc-modality
    restart: unless-stopped
    ports: ["8044:8042"]
    volumes: ["orthanc-storage-modality:/var/lib/orthanc/db:Z"]
volumes:
  orthanc-storage-pacs:
  orthanc-storage-middleman:
  orthanc-storage-modality:

Now I replaced the docker image used in the orthanc containers (to save some memory):

instead of orthancteam/orthanc I switched to jodogne/orthanc-plugins:1.12.4

now the persistent saving of patient data is not working anymore.

Is there a plugin or configuration I can use to fix the persistent saving to docker volumes?

here my orthanc.json:


{
  "Name": "Orthanc-modality",
	"RemoteAccessAllowed" : true,
	"AuthenticationEnabled" : true,
	"RegisteredUsers" : {
		"demo": "demo"
	},
  "DicomAet": "MODALITY",
  "DicomModalities": {
      "pacs": ["PACS", "orthanc-pacs", 4242], // to perform query-retrieve on the PACS
      "middleman": ["MIDDLEMAN", "orthanc-middleman", 4242] // used as a C-Store destination
  }
},
  "Plugins" : [
    "/usr/share/orthanc/plugins", "/usr/local/share/orthanc/plugins"
  ]
2

Hello

This could be related to permissions. By default, the Orthanc Team images run as root, if I am not mistaken. If these folders that you’re mapping belong to root, the default images from Sébastien, running with user orthanc, could have issues using them. That is just an hypothesis.

To check this, I would exec a shell in your container, navigate to /var/lib/orthanc/db, and make sure that you can examine the containers of the bound folder from there : that adding a file at that location, from the container, can be seen on the host, and the opposite, and that the container is able to write.

Another quick test you can make is chmod -R 777 on all of them before starting the compose file.

Let us know how it goes!

HTH

Benjamin