NEMO2/Containers: Difference between revisions

From bwHPC Wiki
Jump to navigation Jump to search
(Created page with "NEMO supports two container runtimes for different use cases. Neither requires root privileges and both integrate with the cluster's shared filesystems (<tt>/home</tt>, <tt>/work</tt>). == Overview == {| class="wikitable" |- ! ! Enroot + Pyxis (recommended) ! Apptainer / Singularity |- | '''Image source''' | Docker Hub, NGC, any OCI registry | Apptainer Hub, Docker (via conversion), SIF files |- | '''Image format''' | Squa...")
 
mNo edit summary
 
(2 intermediate revisions by the same user not shown)
Line 7: Line 7:
|-
|-
!
!
! [[Containers/Enroot|Enroot + Pyxis]] (recommended)
! [[NEMO2/Containers/Enroot|Enroot + Pyxis]] (recommended)
! [[Containers/Apptainer|Apptainer / Singularity]]
! [[NEMO2/Containers/Apptainer|Apptainer / Singularity]]
|-
|-
| '''Image source'''
| '''Image source'''
| Docker Hub, NGC, any OCI registry
| Docker Hub, NGC, any OCI registry
| Apptainer Hub, Docker (via conversion), SIF files
| Docker Hub, NGC, any OCI registry; SIF files
|-
|-
| '''Image format'''
| '''Image format'''
Line 39: Line 39:
; Enroot + Pyxis
; Enroot + Pyxis
: Use this if you want to run Docker images directly from a registry, submit containerised jobs via <tt>srun</tt>/<tt>sbatch</tt>, or need tight GPU integration.
: Use this if you want to run Docker images directly from a registry, submit containerised jobs via <tt>srun</tt>/<tt>sbatch</tt>, or need tight GPU integration.
: [[Containers/Enroot|→ Enroot & Pyxis details]]
: [[NEMO2/Containers/Enroot|→ Enroot & Pyxis details]]


; Apptainer
; Apptainer
: Use this if you have an existing <tt>.sif</tt> image, are working with a workflow that builds Apptainer/Singularity images, or need a self-contained portable image you can copy between systems.
: 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.
: [[Containers/Apptainer|→ Apptainer details]]
: [[NEMO2/Containers/Apptainer|→ Apptainer details]]


== Note on Docker ==
== Note on Docker ==


Plain Docker is '''not available''' on NEMO. Use Enroot to pull and run Docker images, or build a <tt>.sif</tt> with Apptainer on a machine where you have Docker installed and copy it over.
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.

Retrieved from "https://wiki.bwhpc.de/wiki/index.php?title=NEMO2/Containers&oldid=16061"