Deployed ad88c05 with MkDocs version: 1.5.3

user-guide/singularity/index.html

@@ -1605,7 +1605,7 @@ <h3 id="parallel-processes-within-a-non-interactive-batch-script">Parallel proce
 module load singularity
 
 # The host bind paths for the Singularity container.
-BIND_ARGS=/scratch/sw,/opt/hpe,/etc/libibverbs.d,/path/to/input/files
+BIND_ARGS=/mnt/lustre/indy2lfs/sw,/opt/hpe,/etc/libibverbs.d,/path/to/input/files
 
 # The file containing environment variable settings that will allow
 # the container to find libraries on the host, e.g., LD_LIBRARY_PATH . 
@@ -1710,17 +1710,17 @@ <h3 id="accessing-cirrus-modules-from-inside-a-container">Accessing Cirrus Modul
 </code></pre>
 <p>The resulting image file (<code>centos7.sif</code>) can then be copied to Cirrus
 using scp; such an image already exists on Cirrus and can be found in
-the <code>/scratch/sw/singularity/images</code> folder.</p>
+the <code>/mnt/lustre/indy2lfs/sw/singularity/images</code> folder.</p>
 <p>When you use that image interactively on Cirrus you must start with a
-login shell and also bind <code>/scratch/sw</code> so that the container can see
-all the module files, see below.</p>
+login shell and also bind <code>/mnt/lustre/indy2lfs/sw</code> so that the container
+can see all the module files, see below.</p>
 <pre><code>[user@cirrus-login1 ~]$ module load singularity
-[user@cirrus-login1 ~]$ singularity exec -B /scratch/sw \
-  /scratch/sw/singularity/images/centos7.sif \
+[user@cirrus-login1 ~]$ singularity exec -B /mnt/lustre/indy2lfs/sw \
+  /mnt/lustre/indy2lfs/sw/singularity/images/centos7.sif \
     /bin/bash --login
 Singularity&gt; module avail intel-compilers
 
-------------------------- /scratch/sw/modulefiles ---------------------
+--------- /mnt/lustre/indy2lfs/sw/modulefiles -------------
 intel-compilers-18/18.05.274  intel-compilers-19/19.0.0.117
 Singularity&gt; exit
 logout
@@ -1735,10 +1735,10 @@ <h3 id="altering-a-container-on-cirrus">Altering a Container on Cirrus</h3>
 followed by a <code>shell</code> command with the <code>--writable</code> option. You are now
 free to change the files inside the container sandbox.</p>
 <pre><code>user@cirrus-login1 ~]$ singularity build --sandbox image.sif.sandbox image.sif
-user@cirrus-login1 ~]$ singularity shell -B /scratch/sw --writable image.sif.sandbox
+user@cirrus-login1 ~]$ singularity shell -B /mnt/lustre/indy2lfs/sw --writable image.sif.sandbox
 Singularity&gt;
 </code></pre>
-<p>In the example above, the <code>/scratch/sw</code> bind path is specified, allowing
+<p>In the example above, the <code>/mnt/lustre/indy2lfs/sw</code> bind path is specified, allowing
 you to build code that links to the Cirrus module libraries.</p>
 <p>Finally, once you are finished with the sandbox you can exit and convert
 back to the original image file.</p>