Files
ilkerandClaude Opus 5 a6d453ae7b hpcod: application images, and a catalogue generated from them
The catalogue published one image. Filling it is not nine more
Containerfiles: it is a question of who compiles the software, against
which MPI, and how a second cluster gets it without paying for the
first one's build. image/apps holds the answer to the first of those -
one driver over one directory per application, with three recipes
(somebody else's image, one we assemble, or Spack against our own MPI)
and the rule for choosing between them.

The catalogue is generated from the recipes rather than kept beside
them, because an entry in it is a promise that a head node can pull the
image, and a promise nobody checks is how the first generated catalogue
came to point busybox at a tag that had never existed - guessed from
the upstream version instead of read from the registry. The generator
now asks the registry, and an application whose image is not there is
reported rather than offered.

Recipes are intent and published.json is measurement, kept apart so
that recording the hash of a push does not rewrite the reasoning in the
recipe that produced it.

Two entries to start: busybox, which is the cheapest way to prove the
whole delivery path, and stress-ng, which is what somebody actually
runs first on a cluster they have just been handed.

docs/22 is the Spack half of the question, from reading Chapar: what it
would give us, the three levels of integration, and the PMIx version to
settle on a real head before a single image is built against it.

Two things about the build host, both found by trying: Apptainer is not
installed, and Docker is, which sets FORWARD DROP and leaves podman
unable to build anything that needs the network.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-09-22 10:25:37 +02:00
..