I am trying to run pennlinc/qsiprep:26.0.0 converted to a Singularity image with GPU support:
singularity run --nv qsiprep-26.0.0.simg ...
Two issues appear.
First, QSIPrep selects CUDA eddy but looks specifically for eddy_cuda10.2:
Using CUDA and 1 threads in eddy
Cannot run QSIPrep. Missing dependencies:
* eddy_cuda10.2 (Interface: ExtendedEddy)
However, the image contains:
/app/.pixi/envs/qsiprep/bin/eddy_cpu
/app/.pixi/envs/qsiprep/bin/eddy_cuda11.0
A workaround is to bind a wrapper/symlink named eddy_cuda10.2 pointing to eddy_cuda11.0.
Second, after fixing the eddy name issue, DSI Studio fails when running with --nv:
dsi_studio: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.38' not found
(required by /.singularity.d/libs/libGLdispatch.so.0)
dsi_studio: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.38' not found
(required by /.singularity.d/libs/libGLX.so.0)
This happens for commands such as:
dsi_studio --action=src ...
The container uses /opt/dsi-studio/dsi_studio, so this does not seem to be caused by a host-side dsi_studio shadowing the container binary.
Environment:
QSIPrep image: pennlinc/qsiprep:26.0.0 converted to Singularity .simg
Runtime: Singularity with --nv
Command includes: --output-resolution 1.5 --nthreads 16 --omp-nthreads 8 --skip-bids-validation
I am trying to run
pennlinc/qsiprep:26.0.0converted to a Singularity image with GPU support:Two issues appear.
First, QSIPrep selects CUDA eddy but looks specifically for
eddy_cuda10.2:However, the image contains:
A workaround is to bind a wrapper/symlink named
eddy_cuda10.2pointing toeddy_cuda11.0.Second, after fixing the eddy name issue, DSI Studio fails when running with
--nv:This happens for commands such as:
The container uses
/opt/dsi-studio/dsi_studio, so this does not seem to be caused by a host-sidedsi_studioshadowing the container binary.Environment: