Skip to content

Document where the containers are published and how to rebuild them - #190

Merged
rcruces merged 1 commit into
v1from
enning/containers-readme
Nov 12, 2026
Merged

rcruces merged 1 commit into
v1from
enning/containers-readme

Conversation

@zihuaihuai

Copy link
Copy Markdown
Collaborator

Raúl asked where the newest container is and how to rebuild it. Both answers
lived only in the build workspace on BIC and in my own notes, so this writes
them down next to the scripts that do the work.

containers/README.md covers:

  • Where the images are. The two published beta.3 SIFs on
    /data_/mica1/01_programs/singularity/, which variant to take, the files
    beside them, how to verify a checksum, and how to read an image's own
    BUILDINFO.json / CONTAINER_VERSION.
  • How to rebuild. What the host needs, the disk budget, the workspace
    layout build_beta_server.sh expects, and the incremental path that reuses
    the existing BIC workspace — about 15 minutes per variant when only
    micapipe's own code changed.
  • How to fill downloads/ from scratch, item by item, with the upstream
    source for each and which ones SOURCES.sha256 gates. There is no fetch
    script, and that was nowhere written down.
  • The traps: the version stamp comes from versions.json,
    package_beta.sh refuses to overwrite an artifact, and the code tree is
    copied in unguarded so runtime/opt/micapipe has to be removed or you ship
    the old code.
  • Checking a build with the in-image smoke test, and why that is not
    enough on its own — both beta.3 defects passed every static check.
  • Publishing to the shared directory.

Also adds a pointer to it from docs/validation/v1-beta-3.md.

Docs only; no pipeline code touched.

Raul asked where the newest image is and how to rebuild it. Both answers
lived only in the build workspace on BIC and in my own notes, so write them
down next to the scripts: the published paths and how to verify them, the
workspace layout build_beta_server.sh expects, where every item in downloads/
comes from, the incremental-rebuild path that reuses the BIC workspace, the
traps (the version stamp, the refusal to overwrite an artifact, the unguarded
code tree), the in-image smoke test, and the publish step.
@rcruces
rcruces merged commit 8c08f68 into v1 Nov 12, 2026
10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants