Apptainer and Environment Modules¶
On the new platform, environment modules integrate with Apptainer to provide consistent, containerized runtimes for HPC applications. When you module load an application, the module system:
- Resolves and loads required dependencies (e.g.,
gcc,mpi) - Sets per-application environment variables (e.g.,
$EXEC_CMD_VASP,$EXEC_CMD_QE) - Updates a convenience variable
$EXEC_CMDto the most recently loaded application's command - Maintains
$EXEC_CMDSas a colon-separated list of loaded application exec variables (e.g.,EXEC_CMD_VASP:EXEC_CMD_QE)
Example session¶
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 | |
Notes:
- The Apptainer command binds common platform directories into the container (e.g., /export, /scratch, /dropbox, and the cluster share such as /cluster-001-share).
- $EXEC_CMD always points to the last loaded application's container exec command.
- Use per-app variables (e.g., $EXEC_CMD_VASP, $EXEC_CMD_QE) when you need to be explicit in job scripts.
Using in job scripts¶
See: - Jobs via Command Line - Batch Scripts > General Structure - Batch Scripts > Sample Scripts