You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Dicom images can be sent to MD express where it would be stored then initiate a pipeline.
Requesting to have a way to delete this dicom data after X hours from the task being completed/failed.
May be have a storage disk limit in Gb or something. Otherwise if we leave the system up long enough we would run out of disk space
One workaround may be to use shared volumes in the docker compose as
volumes: { incoming-dicom-data: {} }
Then instruct user to delete that volume after as
docker compose down
docer volume rm incoming-dicom-data
The text was updated successfully, but these errors were encountered:
Using a volume actually makes sense because it also provides a solution to file resolution issues whilst running from within a container. I will be submitting PR for this.
Dicom images can be sent to MD express where it would be stored then initiate a pipeline.
Requesting to have a way to delete this dicom data after X hours from the task being completed/failed.
May be have a storage disk limit in Gb or something. Otherwise if we leave the system up long enough we would run out of disk space
One workaround may be to use shared volumes in the docker compose as
Then instruct user to delete that volume after as
The text was updated successfully, but these errors were encountered: