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
Just a minor suggestion to improve quality of living when using singularity or docker:
Currently pulling the container docker://nistmni/minc-toolkit:1.9.16 works great, except all programs must be run with /opt/min/1.9.16/bin/. For example singularity exec minc-toolkit_1.9.16.sif /opt/min/1.9.16/bin/nii2mnc correctly returns the usage for this executable.
Simply adding the following line to the Dockerfile and rebuilding the container would make this much easier to use: ENV PATH /opt/min/1.9.16/bin:$PATH. The above command would now be singularity exec minc-toolkit_1.9.16.sif nii2mnc
Thanks!
The text was updated successfully, but these errors were encountered:
Looks like that would do it! I guess I just needed to pull the latest image.
Perhaps that could be updated in the documentation? e.g. docker pull nistmni/minc-toolkit:1.9.16 could be changed to docker pull nistmni/minc-toolkit:latest assuming that this would only be stable releases.
Just a minor suggestion to improve quality of living when using singularity or docker:
Currently pulling the container
docker://nistmni/minc-toolkit:1.9.16
works great, except all programs must be run with/opt/min/1.9.16/bin/
. For examplesingularity exec minc-toolkit_1.9.16.sif /opt/min/1.9.16/bin/nii2mnc
correctly returns the usage for this executable.Simply adding the following line to the Dockerfile and rebuilding the container would make this much easier to use:
ENV PATH /opt/min/1.9.16/bin:$PATH
. The above command would now besingularity exec minc-toolkit_1.9.16.sif nii2mnc
Thanks!
The text was updated successfully, but these errors were encountered: