Repository navigation
v0.0.12
runnerd 0.0.12
Before you upgrade
The job history stays at version 12, so 0.0.11 still reads it. Move each profile's image to its -0.0.12 tag:
the Docker store fix lives in the images. Upgrading has the steps.
Fixed
- Each slot now keeps its Docker images and build cache between jobs. Sysbox mounted a directory of its own
over the data root the image'sdaemon.jsonnamed and deleted it with the container, so every runner started
with an empty Docker store: every image build re-extracted its base with no cached steps, and Testcontainers
pulled its images again on every job. The engine now gets its data root as a flag, on the slot's volume. - A slot whose Docker store is damaged, by a crash or a full disk, has it emptied and its engine started again,
instead of failing every runner that lands there. - A snapshot over its
snapshot_maxstarts over at its profile's next idle moment, whateverreseed_atsays.
New
- Pull requests from a repository's own branches can write to the build cache. Set
build_cache_writers = "pull-requests"under a repository. Then a merge tomain, which builds what its pull
request's last run built, finds that build in the cache. GitHub's API decides who acted. Forks, Renovate,
Dependabot and other bots still only read, and the run's commit must be on its branch. - The slots' Docker stores share a quarter of the disk not otherwise used, measured, with nothing to set.
After a job, the build cache is trimmed first, and images are dropped only when the store is still over its share. - The volumes of slots past a lowered slot count are removed at the next moment no job runs.
Download runnerd 0.0.12
| File | Platform | Checksum |
|---|---|---|
| runnerd-aarch64-unknown-linux-musl.tar.xz | ARM64 MUSL Linux | checksum |
| runnerd-x86_64-unknown-linux-musl.tar.xz | x64 MUSL Linux | checksum |
Verifying GitHub Artifact Attestations
The artifacts in this release have attestations generated with GitHub Artifact Attestations. These can be verified by using the GitHub CLI:
gh attestation verify <file-path of downloaded artifact> --repo ayagmar/runnerdYou can also download the attestation from GitHub and verify against that directly:
gh attestation verify <file-path of downloaded artifact> --bundle <file-path of downloaded attestation> --repo ayagmar/runnerdrunnerd-cli 0.0.12
Download runnerd-cli 0.0.12
| File | Platform | Checksum |
|---|---|---|
| runnerd-cli-aarch64-unknown-linux-musl.tar.xz | ARM64 MUSL Linux | checksum |
| runnerd-cli-x86_64-unknown-linux-musl.tar.xz | x64 MUSL Linux | checksum |
Verifying GitHub Artifact Attestations
The artifacts in this release have attestations generated with GitHub Artifact Attestations. These can be verified by using the GitHub CLI:
gh attestation verify <file-path of downloaded artifact> --repo ayagmar/runnerdYou can also download the attestation from GitHub and verify against that directly:
gh attestation verify <file-path of downloaded artifact> --bundle <file-path of downloaded attestation> --repo ayagmar/runnerd