Bureaucrats, cc_docs_admin, cc_staff
2,306
edits
Singularity: Difference between revisions
Jump to navigation
Jump to search
no edit summary
m (Adding scenario of specifying mount point to be seen within container) |
No edit summary |
||
| Line 364: | Line 364: | ||
* <code>/scratch</code> so that the scratch directory can be accessed (subject to your account's permissions) | * <code>/scratch</code> so that the scratch directory can be accessed (subject to your account's permissions) | ||
* <code>/localscratch</code> so that the localscratch directory can be accessed (subject to your account's permissions) | * <code>/localscratch</code> so that the localscratch directory can be accessed (subject to your account's permissions) | ||
In the final item we demonstrate how we can change the mount name that is visible within the Singularity container, so that <code>/localscratch</code> will be seen as <code>/temp</code> inside the container. This can be useful when you want to use storage like <code>$SLURM_TMPDIR</code> which is attached directly to the compute node and available inside a job. The program itself can abstract away the details by always using <code>/temp</code>. | |||
<!--T:92--> | <!--T:92--> | ||