Skip to main content
v2026.11,772 entries · CC-BY 4.0
Dictionary termTrack CStablev2026.2

Container image (Docker/Singularity/Apptainer)

A packaged, immutable filesystem and configuration that contains an application together with all its dependencies, runnable identically on any compatible container engine (Docker, Podman, Singularity, Apptainer). A Singularity container specifically refers to this artifact built or run via the Singularity/Apptainer engine -- a single portable .sif image file executed without a privileged daemon.

ByCASRAI Editorial Board
· Last updated 1 Sept 2026
Share this

Ask CASRAI · included with Regulatory Radar

Ask about Container image (Docker/Singularity/Apptainer)

Ask CASRAI answers research-administration questions and cites the passages behind every claim — and says so when the corpus does not cover something, instead of guessing. It comes with a Regulatory Radar subscription at $29 a month, alongside the daily digest of regulatory changes and the dashboard of what changed.

150 questions a day, on this site, over the API, or inside your own tools through the CASRAI MCP server.

Everything CASRAI publishes — this page, the dictionary, the guides and the news — stays free to read, with no account and no card.

Examples

Worked examples

  • Is an instance

    An analysis distributed as a Docker image pinned by SHA-256 digest in a paper's reproducibility appendix.

  • Is an instance

    A bioinformatics image hosted on Quay.io referenced by a Nextflow pipeline.

  • Is an instance

    A shared HPC cluster running a bioinformatics workload from a .sif file via Singularity/Apptainer, with no root access requested or granted.

Counter-examples

Looks similar, but isn't

  • Not an instance

    A virtual-machine image (heavier and less portable).

  • Not an instance

    A conda environment YAML (specifies environment but not OS/runtime).

Editorial commentary

A container image is a packaged, immutable filesystem bundling an application together with every dependency it needs to run — system libraries, language runtime, configuration — built from a build specification (a Dockerfile for Docker, or a definition file for Singularity/Apptainer) and runnable identically across compatible host machines via a container engine.

Docker versus Singularity/Apptainer — why research computing generally uses the latter

Docker is the dominant container engine for general software deployment, but its daemon model requires root-equivalent privileges to run containers, which most shared HPC clusters will not grant to individual users. Singularity was created specifically to solve this for scientific and HPC computing: it runs containers without a privileged daemon, mapping the container process to the invoking user’s own permissions, while still consuming standard OCI/Docker-format images. In 2021 the open-source Singularity project moved to the Linux Foundation and was renamed Apptainer to resolve a naming and trademark conflict with a commercial fork, SingularityCE, maintained by Sylabs, which continued under the original name — so Singularity and Apptainer today refer to two actively maintained, closely related but organisationally separate projects descended from the same original codebase, and a citation should specify which one was actually used.

Running a Singularity container

In practice, a Singularity container is a single portable image file in Singularity Image Format (a .sif file), built once from a definition file or converted from an existing Docker/OCI image, then executed directly with no daemon and no elevated privileges required. This is the pattern documented by Sylabs’ own user guides and by university and government HPC centers alike: a shared cluster can let a researcher run a containerized workload inside a scheduled batch job without granting that user root access anywhere on the system.

Why it matters for reproducibility

A container image is one concrete mechanism for capturing a computational environment; sharing the image or its build file alongside code and data is now standard practice for computational reproducibility, and several journals now request it explicitly.

References

Also known as

Docker image · Singularity image · Apptainer image · OCI image · Singularity container

Machine-readable encodings

Use in your systems

JATS XML <role> element
xml
<role vocab="credit"
      vocab-identifier="https://casrai.org/dictionary/"
      vocab-term="Container image (Docker/Singularity/Apptainer)"
      vocab-term-identifier="https://casrai.org/dictionary/term/container-image-docker-singularity-apptainer" />
Schema.org DefinedTerm (JSON-LD)
json
{
  "@context": "https://schema.org",
  "@type": "DefinedTerm",
  "@id": "https://casrai.org/dictionary/term/container-image-docker-singularity-apptainer",
  "name": "Container image (Docker/Singularity/Apptainer)",
  "identifier": "https://casrai.org/dictionary/term/container-image-docker-singularity-apptainer",
  "description": "A packaged, immutable filesystem and configuration that contains an application together with all its dependencies, runnable identically on any compatible container engine (Docker, Podman, Singularity, Apptainer). A Singularity container specifically refers to this artifact built or run via the Singularity/Apptainer engine -- a single portable .sif image file executed without a privileged daemon.",
  "inDefinedTermSet": "https://casrai.org/dictionary/domain/reproducibility#set",
  "url": "https://casrai.org/dictionary/term/container-image-docker-singularity-apptainer",
  "sameAs": [
    "Docker image",
    "Singularity image",
    "Apptainer image",
    "OCI image",
    "Singularity container"
  ],
  "license": "https://creativecommons.org/licenses/by/4.0/",
  "publisher": {
    "@id": "https://casrai.org/#organization"
  },
  "author": {
    "@id": "https://casrai.org/#editorial-team"
  },
  "datePublished": "2026-05-21T02:22:49",
  "dateModified": "2026-09-01T02:12:06",
  "inLanguage": "en-GB",
  "isAccessibleForFree": true
}

Referenced across the research world

University of Cambridge logoColumbia University logoCrossref logoUniversity of Edinburgh logoHarvard University logoUniversity of Oxford logoPrinceton University logoStanford School of Medicine logoUniversity College London logoORCID logoUniversity of Cambridge logoColumbia University logoCrossref logoUniversity of Edinburgh logoHarvard University logoUniversity of Oxford logoPrinceton University logoStanford School of Medicine logoUniversity College London logoORCID logo
  • University of Cambridge logo
  • Columbia University logo
  • Crossref logo
  • University of Edinburgh logo
  • Harvard University logo
  • University of Oxford logo
  • Princeton University logo
  • Stanford School of Medicine logo
  • University College London logo
  • ORCID logo

View CASRAI adoption →

Regulatory Radar

Stop finding out after the fact

$29/month, cancel anytime. Daily digest updates from our analysis, a dashboard holding the same items, and a cited assistant for everything they raise.

  • Federal Register, Federal Register+, Grants.gov, Regulations.gov, NSF News, UKRI, plus CASRAI’s own published content.
  • 72,264 indexed passages, and every answer cites the ones it drew on.