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
HPC no longer supports /30days and so the bindpaths seem to make the container build fail when fetching freesurfer
(run on awoonga)
checking if container needs to be downloaded
pulling image now ...
% Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed
100 2395M 100 2395M 0 0 11.9M 0 0:03:20 0:03:20 --:--:-- 12.5M
checking which executables exist inside container
executing:
singularity exec --pwd /home/uqtshaw/neurodesk/local/containers/freesurfer_7.1.1_20210225 freesurfer_7.1.1_20210225.simg
/home/uqtshaw/neurodesk/local/containers/freesurfer_7.1.1_20210225/ts_binaryFinder.sh FATAL: container
creation failed: mount /30days->/30days error: while mounting /30days: mount source /30days doesn't exist
checking if commands.txt exists now
[DEBUG] run_transparent_singularity: Trying to set singularity bindpaths:
FATAL: container creation failed: mount /30days->/30days error: while mounting /30days: mount source /30days doesn't exist
[DEBUG] run_transparent_singularity: Something is wrong with the Singularity Bindpath. Please check!
The text was updated successfully, but these errors were encountered:
@thomshaw92
This looks like an issue with the singularity configuration on the HPC
Does this error occur when opening a generic singularity container on the same HPC?
Yes, this is an issue with awoonga - not our containers. I already send a helpdesk ticket. Workaround is to use singularity 2.6.1 as this just shows a warning but still executes the container with wrong global bindpaths.
HPC no longer supports /30days and so the bindpaths seem to make the container build fail when fetching freesurfer
(run on awoonga)
The text was updated successfully, but these errors were encountered: