packages.x86_64-linux.zot
- system
- x86_64-linux
- status
- cached
- started
- —
- finished
- 2026-09-13 10:01:56 UTC
- total
- —
- image size
- 33.19 MB
- derivation
- /nix/store/wh14s2fhyx9r2myjhv3h8b8npf0qhmlz-docker-image-zot.tar.gz.drv
- output
- /nix/store/02fbsdbj8a9d2021lksh283hvb3nqmpk-docker-image-zot.tar.gz
Run from registry
docker run --rm registry.stack4ops.com/stack4ops/images/zot:latest
Pulls the image straight from the registry argunix pushed it to —
no Nix required. podman run works
the same way.
registry & effects
What argunix did with this build's output after it was realised — pushing the image to a registry, attaching its SBOM. The detail line of a registry push is the reference you pull.
| effect | status | detail |
|---|---|---|
| registry-push · zot | success | pushed registry.stack4ops.com/stack4ops/images/zot:main, registry.stack4ops.com/stack4ops/images/zot:latest, registry.stack4ops.com/stack4ops/images/zot:sha-bac3d98f1eb0 to zot |
| sbom-attach · zot | success | attached SBOM (8 components) to registry.stack4ops.com/stack4ops/images/zot:sha-bac3d98f1eb0 |