NEMO2/Containers: Difference between revisions
< NEMO2
Jump to navigation
Jump to search
mNo edit summary |
mNo edit summary |
||
| (One intermediate revision by the same user not shown) | |||
| Line 12: | Line 12: | ||
| '''Image source''' |
| '''Image source''' |
||
| Docker Hub, NGC, any OCI registry |
| Docker Hub, NGC, any OCI registry |
||
| |
| Docker Hub, NGC, any OCI registry; SIF files |
||
|- |
|- |
||
| '''Image format''' |
| '''Image format''' |
||
| Line 42: | Line 42: | ||
; Apptainer |
; Apptainer |
||
: Use this if you have an existing <tt>.sif</tt> image, |
: Use this if you have an existing <tt>.sif</tt> image, need a self-contained portable image you can copy between systems, or are working with workflows that already use Apptainer/Singularity. |
||
: [[NEMO2/Containers/Apptainer|→ Apptainer details]] |
: [[NEMO2/Containers/Apptainer|→ Apptainer details]] |
||
== Note on Docker == |
== Note on Docker == |
||
Plain Docker is '''not available''' on NEMO. |
Plain Docker is '''not available''' on NEMO. Both Enroot and Apptainer can pull Docker/OCI images directly from registries without a local Docker installation. |
||
Latest revision as of 14:56, 11 May 2026
NEMO supports two container runtimes for different use cases. Neither requires root privileges and both integrate with the cluster's shared filesystems (/home, /work).
Overview
| Enroot + Pyxis (recommended) | Apptainer / Singularity | |
|---|---|---|
| Image source | Docker Hub, NGC, any OCI registry | Docker Hub, NGC, any OCI registry; SIF files |
| Image format | SquashFS (.sqsh) | SIF (.sif) |
| Slurm integration | Native via Pyxis plugin (--container-name etc.) | Manual — wrap in batch script |
| GPU support | Automatic, no extra flags needed | Via --nv flag |
| Installation | System-wide, always available | System-wide, always available |
| Best for | Docker-based workflows, GPU workloads, Slurm batch jobs | Existing SIF images, reproducible science, portability |
When to use what
- Enroot + Pyxis
- Use this if you want to run Docker images directly from a registry, submit containerised jobs via srun/sbatch, or need tight GPU integration.
- → Enroot & Pyxis details
- Apptainer
- Use this if you have an existing .sif image, need a self-contained portable image you can copy between systems, or are working with workflows that already use Apptainer/Singularity.
- → Apptainer details
Note on Docker
Plain Docker is not available on NEMO. Both Enroot and Apptainer can pull Docker/OCI images directly from registries without a local Docker installation.