The image push,
harbor auth login and harbor publish were not run for these docs.1
Push the world image
2
Pin all three images in every task
Pin each image by digest (
repo:tag@sha256:…), for example with sed:- the world, in the compose file’s
image:; miroir-main, in[environment].docker_image;miroir, in[verifier.environment].docker_image.
ghcr.io/raphaeldkhn/miroir
and ghcr.io/raphaeldkhn/miroir-main, tagged <major>.<minor> and
<major>.<minor>.<patch>.3
Lint the tasks
--extend-select unpinned-image checks that all three images are pinned. harbor lint checks
the compose file only with Docker Compose 2.35.0 or later, which has
config --no-env-resolution. An older Compose makes it report invalid-task-config for every
task, so check for the flag first, as above. Pass the task directories (tasks/*/), never
their parent: lint reads each argument as one task.4
Pass the release gate
Run the check job with two attempts:
5
Publish the dataset
harbor run -d me/my-env@1.0.0.Where images must be public
Harbor Hub packages hold the task directories, not the images. Harbor never logs a cloud sandbox’s inner Docker in to a registry, so a world run on Daytona, GKE or Modal must be a public image. A private world runs wherever its image can be pulled: on local Docker afterdocker login, or on
a self-hosted runner with registry access. Hosted Harbor stores
registry credentials for
private task images; whether they reach compose sidecars is not verified.
A publisher’s CI gate
Run this on every change to the world or the tasks, and with-k 2 before a release:
- Build the images.
miroir check --tasks <dir>, for the static checks.- The Compose flag check, then
harbor lint <dir>/*/. harbor run -c check.yaml, thenmiroir check --tasks <dir> jobs/<job>, which must exit 0.
tests/e2e.sh, does this for
the fixture. It then also regrades the job with a changed spec, and checks that a trial without
evidence voids.