Apptainer: Difference between revisions

Jump to navigation Jump to search
no edit summary
No edit summary
No edit summary
Line 288: Line 288:
<!--T:80-->
<!--T:80-->
where:
where:
* <code>-B /home</code> mounts the home filesystem
* <code>-B /home</code> mounts the /home filesystem
* <code>-B /project</code> mounts the project filesystem
* <code>-B /project</code> mounts the /project filesystem
* <code>-B /scratch</code> mounts the scratch filesystem
* <code>-B /scratch</code> mounts the /scratch filesystem


<!--T:81-->
<!--T:81-->
Doing this is especially useful when:
Doing this is especially useful when:
* you need to access others' files on your research time in other locations, and/or,
* you need to access others' files on your research time in other locations, and/or,
* you need to access files/directories some of which are symlinks to different locations that would/might otherwise be broken if you did not mount the entire filesystem.
* you need to access files/directories some of which are <code>symlinks</code> to different locations that would/might otherwise be broken if you did not mount the entire filesystem.


<!--T:82-->
<!--T:82-->
If using these bind mounts do not work on the cluster you are using, then run this script to obtain the bind mount options you need to pass to Apptainer for /home, /project, and /scratch on that cluster:
If using these bind mounts does not work on the cluster you are using, run this next script to obtain the bind mount options you need to pass to Apptainer for /home, /project, and /scratch on that cluster
</translate>
</translate>


Line 314: Line 314:


<!--T:86-->
<!--T:86-->
Finally, <b>don't mount our CVMFS paths</b> inside your containers as this is fraught with perils and defeats many reasons to use a container. The programs needed to be run inside a container need to be completely inside the container --don't introduce even more programs inside the container that don't need to be inside the container.
Finally, <b>don't mount our CVMFS paths</b> inside your containers as this is fraught with perils and defeats many reasons to use a container. The programs that have to run inside a container need to be completely inside the container. Don't introduce even more programs inside the container if they don't need to be there.


==Persistent overlays== <!--T:87-->
==Persistent overlays== <!--T:87-->
rsnt_translations
56,420

edits

Navigation menu