Skip to content
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

problem mounting /30days when downloading Freesurfer image from CLI #76

Closed
thomshaw92 opened this issue Jul 8, 2021 · 2 comments
Closed

Comments

@thomshaw92
Copy link

thomshaw92 commented Jul 8, 2021

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!  
@aswinnarayanan
Copy link
Contributor

aswinnarayanan commented Jul 9, 2021

@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?

e.g.

singularity pull library://alpine
singularity shell alpine_latest.sif

And the following should suppress the auto-mounts
singularity shell --contain alpine_latest.sif

@stebo85
Copy link
Contributor

stebo85 commented Jul 11, 2021

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.

@stebo85 stebo85 closed this as completed Jul 11, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants