checks.x86_64-linux.registry-push
- system
- x86_64-linux
- status
- success
- started
- 2026-06-10 14:07:39 UTC
- finished
- 2026-06-10 14:08:13 UTC
- total
- 34s
- derivation
- /nix/store/fknbqyls7hab1419dk3l9jrzj2j729l5-vm-test-run-argunix-registry-push.drv
- output
- /nix/store/c77vjya0kfvm27m6qdr9cyayldxwgl42-vm-test-run-argunix-registry-push
Run from cache
nix run --extra-experimental-features fetch-closure --accept-flake-config https://argunix.nix-consulting.net/flake/codeberg/tfc/argunix/eval/76#registry-push
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 | 569.30 KB |
| build (net, on builder) | 30s | — |
| pull (output closure ← builder) | 1s | 1.03 KB |
| publish (coord → binary cache) | 165 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 |