-
Notifications
You must be signed in to change notification settings - Fork 13
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
inception mode: running singularity containers in singularity containers #20
Comments
works now :) Trick was to use singularity 3.7.0 and a sandbox directory: |
So cool! |
Correct, this doesn't work yet on most HPCs. It's a future feature :) But it works nicely in our vnm docker container. You can test if your HPC supports it: curl -X GET https://swift.rc.nectar.org.au:8888/v1/AUTH_d6165cc7b52841659ce8644df1884d5e/singularityImages/neurodesk_20210107.sif -O curl -X GET https://swift.rc.nectar.org.au:8888/v1/AUTH_d6165cc7b52841659ce8644df1884d5e/singularityImages/itksnap_3.8.0_20200811.sif -O singularity shell neurodesk_20210107.sif Cheers |
This could be interesting: https://github.com/cvmfs/cvmfsexec Discussion from singularity mailinglist: Another way to move metadata operations to the worker node is the CernVM |
Thanks Steffen. I considered CVMFS for providing a remote standard conda environment in VNM, so let's discuss it as part of AEDAPT. |
Yes, would be good to play with this idea and see if it's viable for distributing our images |
I know it's possible, but it's not working yet. this is how far I got:
https://colab.research.google.com/drive/1WmXStJpD0JTWePCYzK6nLQJ9Kq8Z40dY?usp=sharing
The text was updated successfully, but these errors were encountered: