packages.x86_64-linux.docker
- system
- x86_64-linux
- status
- cached
- started
- —
- finished
- 2026-11-11 19:20:07 UTC
- total
- —
- derivation
- /nix/store/ffrgpwv8qsb0s7pbifn9xdh9qd5x7qqz-docker-image-mkdocs.tar.gz.drv
- output
- /nix/store/i86g83nfh05zp5pm2w9c4xfh7ddbkxxf-docker-image-mkdocs.tar.gz
Run from cache
nix run --extra-experimental-features fetch-closure --accept-flake-config https://argunix.nix-consulting.net/flake/github/applicative-systems/mkdocs-flake/eval/173#docker
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) | — | — |
| build (net, on builder) | — | — |
| pull (output closure ← builder) | — | — |
| publish (coord → binary cache) | 9m 51s | — |
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 |