Containers for CyberShake - Revision history

Llocsin: /* Install Singularity */

2020-08-08T02:09:17Z

Install Singularity

2020-08-08T02:08:58Z

Install Singularity

2020-08-08T02:06:58Z

Resources

2020-08-07T22:32:55Z

Prebuilt Containers

2020-08-07T08:03:03Z

Basic Singularity Commands

2020-08-07T08:02:05Z

Resources

2020-08-07T08:00:02Z

Selection of Containers

2020-08-07T07:59:35Z

Selection of Containers

2020-08-07T07:55:53Z

Build or Pull a Singularity Image

2020-08-07T07:55:20Z

MPI

@@ Line 35: / Line 35: @@
 =====Install Singularity=====
-Check the Release Version [https://github.com/hpcng/singularity/tags]
+Check the Newest Release Version [https://github.com/hpcng/singularity/tags]
 <pre>export VERSION=3.6.1 && # adjust this as necessary \
 wget https://github.com/sylabs/singularity/releases/download/v${VERSION}/singularity-${VERSION}.tar.gz && \

@@ Line 35: / Line 35: @@
 =====Install Singularity=====
-<pre>export VERSION=3.5.2 && # adjust this as necessary \
+Check the Release Version [https://github.com/hpcng/singularity/tags]
 wget https://github.com/sylabs/singularity/releases/download/v${VERSION}/singularity-${VERSION}.tar.gz && \
 tar -xzf singularity-${VERSION}.tar.gz && \
 cd singularity</pre>
 =====Check if Singularity Works=====

← Older revision		Revision as of 02:06, 8 August 2020
Line 318:		Line 318:
	TACC - Frontera		TACC - Frontera
	#TACC Containers [https://github.com/TACC/tacc-containers/tree/master/containers] (More geared for people who are familiar with Docker Containers. Containers do not seem to support singularity exec)		#TACC Containers [https://github.com/TACC/tacc-containers/tree/master/containers] (More geared for people who are familiar with Docker Containers. Containers do not seem to support singularity exec)
		+
		+	ORNL
		+	#Container Builder Tool - [https://github.com/olcf/container-builder]

@@ Line 109: / Line 109: @@
 ==== Prebuilt Containers ====
 ===== Frontera =====
 ===== Summit =====
+Basic Ubuntu with ???
 ==== Building Containers ====

@@ Line 98: / Line 98: @@
 <pre>$ singularity build IMAGE_NAME.sif <source></pre>
 <source> include
--Another Image either docker or singularity
+#Another Image either docker or singularity
--Singularity definition file (use to be known as a recipe file), usually denoted with name.def
+#Singularity definition file (use to be known as a recipe file), usually denoted with name.def

← Older revision		Revision as of 08:02, 7 August 2020
Line 313:		Line 313:

	TACC - Frontera		TACC - Frontera
−	#TACC Containers [https://github.com/TACC/tacc-containers/tree/master/containers] (More geared for people who are familiar with Docker Containers)	+	#TACC Containers [https://github.com/TACC/tacc-containers/tree/master/containers] (More geared for people who are familiar with Docker Containers. Containers do not seem to support singularity exec)

@@ Line 3: / Line 3: @@
 == Selection of Containers ==
-The available HPC Containers at the time of selection were Singularity, Charlie Cloud, and Shifter. Between the 3 of these container technologies, Singularity was widely adapted and had more open source tools. Because of this wide adaptation the module already existed in the Frontera system. Singularity has built-in support for different MPI libraries from OpenMPI, MPICH, and IntelMPI to name a few. Shifter, although light weight, is highly reliant on MPICH ABI. This would require site-specific MPI libraries to be copied to the container at runtime. Charlie Cloud does not have a module in Frontera.
+The available HPC Containers at the time of selection were Singularity, Charliecloud, and Shifter. Between the 3 of these container technologies, Singularity was widely adapted and had more open source tools. Because of this wide adaptation the module already existed in the Frontera system. Singularity has built-in support for different MPI libraries from OpenMPI, MPICH, and IntelMPI to name a few. Shifter, although light weight, is highly reliant on MPICH ABI. This would require site-specific MPI libraries to be copied to the container at runtime. Charliecloud does not have a module in Frontera.
 == Installing Singularity ==

@@ Line 300: / Line 300: @@
 <pre>$ idev -N 1
 $ singularity pull shub://mkandes/ubuntu-mvapich</pre>
-This work on Frontera. MPI Library: mvapich
+*Note: This work on Frontera. MPI Library: mvapich
 ======Execute your command======

@@ Line 141: / Line 141: @@
 ====== MPI ======
 Singularity uses two methods.
-# Bind Approach (cannot be used)
+. Bind Approach (cannot be used)
 You cannot use the bind on a Frontera.
-#Hybrid/Host Approach
+. Hybrid/Host Approach [https://sylabs.io/guides/3.6/user-guide/mpi.html#hybrid-model]
 For MPI containers, you have to use the hybrid approach. Frontera does not support bind.