nixosConfigurations.argunix
- system
- x86_64-linux
- status
- success
- started
- 2026-06-10 14:15:11 UTC
- finished
- 2026-06-10 14:16:47 UTC
- total
- 1m 35s
- derivation
- /nix/store/6x58n0vm3mx6lmh4j1scsjwilz4cp52s-nixos-system-argunix-26.11.20260606.a799d3e.drv
- output
- /nix/store/c8x4f7x1xzv4r1kys5lfskswczyakrz2-nixos-system-argunix-26.11.20260606.a799d3e
Run from cache
nix run --extra-experimental-features fetch-closure --accept-flake-config https://argunix.nix-consulting.net/flake/codeberg/tfc/argunix/eval/77#argunix
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) | 2s | 605.20 KB |
| build (net, on builder) | 3s | — |
| pull (output closure ← builder) | 1m 29s | 5.57 MB |
| publish (coord → binary cache) | 3s | — |
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 |