packages.x86_64-linux.voidshield
- system
- x86_64-linux
- status
- success
- started
- 2026-05-24 08:46:35 UTC
- finished
- 2026-05-24 08:50:14 UTC
- total
- 3m 39s
- image size
- 36.97 MB
- derivation
- /nix/store/mzaa101iml2lbxyqsms906ry3wqz91x6-voidshield.tar.gz.drv
- output
- /nix/store/dhay3dlixlc4hmixasn7yrbvbrpdxysv-voidshield.tar.gz
Run from registry
docker run --rm forge.zitrone44.de/zitrone44/voidshield:latest
Pulls the image straight from the registry argunix pushed it to —
no Nix required. podman run works
the same way.
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) | 459 ms | 237.05 KB |
| build (net, on builder) | 3m 38s | — |
| pull (output closure ← builder) | 146 ms | 920 B |
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 |
|---|---|---|
| registry-index · forge | success | assembled 2-arch index (arm64+amd64, 2 per-arch SBOMs) → forge.zitrone44.de/zitrone44/voidshield:main, latest, sha-a866b61ea128 |