checks.x86_64-linux.build-in-container
- system
- x86_64-linux
- status
- success
- started
- 2026-08-02 19:52:17 UTC
- finished
- 2026-08-02 19:55:07 UTC
- total
- 2m 50s
- derivation
- /nix/store/9i1yb4k4vhn6nbx1zhxrxwb28w8xnggy-vm-test-run-nix-image-build-in-container.drv
- output
- /nix/store/4l2r52071zjikxak4ifbv30rykfv5pkp-vm-test-run-nix-image-build-in-container
Run from cache
nix run --extra-experimental-features fetch-closure --accept-flake-config https://argunix.nix-consulting.net/flake/opencode/oci-community/images/applicative-systems/nix/eval/139#build-in-container
Requires this argunix's cache in
trusted-substituters +
trusted-public-keys — see
/cache for
the one-time setup snippet.
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) | 15s | 206.43 MB |
| build (net, on builder) | 2m 34s | — |
| pull (output closure ← builder) | 439 ms | 1.04 KB |
| publish (coord → binary cache) | 645 ms | — |
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-push · opencode | skipped | not a container image |
| sbom-attach · opencode | skipped | not a container image |