Replies: 1 comment 5 replies
-
Guess there is an issue with the persistence of your DB volume. arc:
..
volumes:
- fs:/storage so stored objects will get lost by recreation of containers. You also missed to map out ldap configuration ( |
Beta Was this translation helpful? Give feedback.
5 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Describe the bug
When restarting the archive via Docker compose, I am getting an internal server error (see trace-stack below as well as ImagingDataCommons/slim#43).
We only slightly adapted the example provided in the wiki to use Docker volumes instead of bind mounts for improved cross-platform compatibility (see https://github.com/MGHComputationalPathology/slim/blob/master/docker-compose.yml).
To Reproduce
Steps to reproduce the behavior:
git clone https://github.com/MGHComputationalPathology/slim /tmp/slim
cd tmp/slim
docker-compose up -d
curl -I http://localhost:8008/dicomweb/studies
=> 204 No Contentdicomweb_client -vv --url http://localhost:8008/dicomweb store instances ${FILEPATH}
curl -I http://localhost:8008/dicomweb/studies
=> 200 OKcurl -I http://localhost:8008/dicomweb/studies/${STUDY_UID}/metadata
=> 200 OKdocker-compose down
docker-compose up -d
curl -I http://localhost:8008/dicomweb/studies
=> 200 OKcurl -I http://localhost:8008/dicomweb/studies/${STUDY_UID}/metadata
=> 500 Internal Server ErrorExpected behavior
Expected archive to work after a restart.
Beta Was this translation helpful? Give feedback.
All reactions