@@ -349,9 +349,17 @@ or you can set the global variable to what you want to use (it defaults to lmod)
349
349
$ shpc config set module_sys:tcl
350
350
351
351
352
- The command line argument, if provided, always over-rides the default. The
353
- same works for the container technology. Here is how to install with a different
354
- container technology, podman, either for a one-off command:
352
+ The command line argument, if provided, always over-rides the default.
353
+
354
+
355
+ Container Technology
356
+ ====================
357
+
358
+ The default container technology to pull and then provide to users is Singularity,
359
+ and we have also recently added Podman, and will add support for Shifter and Sarus soon.
360
+ Akin to module software, you can specify the container technology to use on a global
361
+ setting, or via a one-off command:
362
+
355
363
356
364
.. code-block :: console
357
365
@@ -365,15 +373,8 @@ or for a global setting:
365
373
$ shpc config set container_tech:podman
366
374
367
375
368
-
369
- Container Technology
370
- ====================
371
-
372
- The default container technology to pull and then provide to users is Singularity,
373
- which makes sense because we can add executables to the path that are Singularity containers.
374
- We have also recently added Podman, and will add support for Shifter and Sarus soon.
375
- If you would like support for a different container technology, please also
376
- `open an issue <https://github.com/singularityhub/singularity-hpc >`_ and
376
+ If you would like support for a different container technology that has not been
377
+ mentioned, please also `open an issue <https://github.com/singularityhub/singularity-hpc >`_ and
377
378
provide description and links to what you have in mind.
378
379
379
380
.. _getting_started-commands :
0 commit comments