-
Notifications
You must be signed in to change notification settings - Fork 62
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Container exists immediately after running #437
Comments
Perhaps this is because of how the entrypoint for the container is defined: https://github.com/QIICR/dcmqi/blob/master/docker/dcmqi/imagefiles/docker_entry.sh. The easiest might be to make a new docker image from qiicr/dcmqi.
|
I'm experiencing the same problem on Debian 11. I tried your solution @fedorov and the container still exits with 139. |
I confirm it currently works for me on mac as below. I have not yet tested on other platforms.
|
Yeah it's a strange one, I haven't had time to debug more but I just tired your output:
I'll likely check this out in the coming week. Just quickly how does this project compare to the Slicer extension? I feel like I get the impression that may be more supported than the cli? |
The Slicer extension is a wrapper around dcmqi CLIs. I have not been able to find much time to invest into dcmqi. I feel like dcmqi serves a certain need in its current state, implementation of drastically new features is complex due to dependency on DCMTK for lower-level functionality, which is not easy to extend. Regarding this specific issue you are facing, I would definitely appreciate any help, since my experience with docker is rather basic. Right now the main feature I want to make the time to implement is
I am sorry for such a delay in responding to your question. |
@fedorov No worries on the time to reply! no pressure here. I'm currently using the slicer extension to prove a process I'm working on, soon I'll likely come back to this project and the container image to better automate the process. I'm fairly comfortable with Docker but I've never encountered it crashing immediately, so it'll be an interesting debug. Do you think the old ITK build difference between the container and slicer could have any influence in this issue? I'll keep you posted when I get a chance, and if I find anything interesting. |
Hi,
Thank you so much for your package.
I have a problem with docker container for qiicr/dcmqi.
After running it exits immediately with exited (139). I tried all the below commands but they don't work.
I would be grateful if you help me.
Best.
The text was updated successfully, but these errors were encountered: