nixosConfigurations.ingress
- system
- x86_64-linux
- status
- success
- started
- 2026-09-10 19:34:41 UTC
- finished
- 2026-09-10 20:31:39 UTC
- total
- 56m 58s
- derivation
- /nix/store/pwqpkcrw47ar6v9l5apv6949i9r2bw8m-nixos-system-ingress-26.05.20260910.d58a46e.drv
- output
- /nix/store/yh0na2rw2l2c68x6g9m4zkglw4zvlcxx-nixos-system-ingress-26.05.20260910.d58a46e
Run from cache
nix run --extra-experimental-features fetch-closure --accept-flake-config https://argunix.snyssen.be/flake/github/snyssen/mother-of-all-infra/eval/314#ingress
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) | 1s | 415.02 KB |
| build (net, on builder) | 5m 59s | — |
| pull (output closure ← builder) | 803 ms | 398.02 KB |
| publish (coord → binary cache) | 5m 0s | — |
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 | failure | `nix copy --to s3://cache?endpoint=https://s3.snyssen.be®ion=home` timed out after 300s |