packages.x86_64-linux.nix
- system
- x86_64-linux
- status
- success
- started
- 2026-08-02 06:47:26 UTC
- finished
- 2026-08-02 06:47:35 UTC
- total
- 9s
- image size
- 102.85 MB
- derivation
- /nix/store/j36mb612xwcd7mgvmvlh3qdzrl6ia77k-docker-image-nix.tar.gz.drv
- output
- /nix/store/7whkigsk06amdjh24lxm6mhr82hmdbay-docker-image-nix.tar.gz
Run from registry
docker run --rm registry.opencode.de/oci-community/images/applicative-systems/nix/nix:latest
Pulls the image straight from the registry argunix pushed it to —
no Nix required. podman run works
the same way.
transport & build
Time and data spent uploading the build inputs to the builder, running the build, and downloading the outputs back. Bytes are measured between argunix and the builder; the build duration is the build itself, not including transfer.
| phase | duration | bytes |
|---|---|---|
| push (drv closure → builder) | 1s | 6.80 MB |
| build (net, on builder) | 6s | — |
| pull (output closure ← builder) | 1s | 102.85 MB |
| publish (coord → binary cache) | 58s | — |
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 |
|---|---|---|
| cache-push · s3://test-cache?endpoint=nbg1.your-objectstorage.com®ion=nbg1&addressing-style=virtual | success | pushed output closure to s3://test-cache?endpoint=nbg1.your-objectstorage.com®ion=nbg1&addressing-style=virtual |
| registry-index · opencode | success | assembled 1-arch index (amd64, 1 per-arch SBOM, 1 attested) → registry.opencode.de/oci-community/images/applicative-systems/nix/nix:main, latest, sha-5be3e4530968 (missing arch: aarch64-linux) |