packages.x86_64-linux.container
- system
- x86_64-linux
- status
- success
- started
- 2026-08-04 01:23:16 UTC
- finished
- 2026-08-04 01:27:35 UTC
- total
- 4m 19s
- derivation
- /nix/store/zry612zwkyiqn9k0i0ksmgahc64zv2s5-personal-website.tar.gz.drv
- output
- /nix/store/gjmd08zvcsw50p7gnnrmh02094jxrkw4-personal-website.tar.gz
Run from cache
nix run --extra-experimental-features fetch-closure --accept-flake-config https://argunix.snyssen.be/flake/github/snyssen/personal-website/eval/49#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) | 756 ms | 402.51 KB |
| build (net, on builder) | 4m 17s | — |
| pull (output closure ← builder) | 132 ms | 1.41 KB |
| publish (coord → binary cache) | 2m 12s | — |
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://cache?endpoint=https://s3.snyssen.be®ion=home | success | pushed output closure to s3://cache?endpoint=https://s3.snyssen.be®ion=home |