ddd
Some checks failed
Deploy control plane / Build, push, and deploy production (push) Failing after 10s
Release VPS agent / Build and publish Linux agent (push) Failing after 1m8s

This commit is contained in:
2026-09-24 23:39:54 +03:00
parent d912da6310
commit d8f98497b5
6 changed files with 53 additions and 32 deletions

View File

@@ -12,14 +12,16 @@ Register an amd64 Gitea Actions runner whose `ubuntu-latest` label resolves to a
Linux environment with:
- `bash`, `curl`, `jq`, `file`, `sha256sum`, Git, and CA certificates;
- Docker with permission for the runner user to access its daemon;
- outbound access to the Rust registries and the container registry used by
`cross`.
- Docker with Buildx and permission for the runner user to access its daemon;
- permission to start the pinned `tonistiigi/binfmt` helper as privileged so it
can register the arm64 emulator;
- outbound access to Docker Hub and the Rust package registry.
When Rustup or Cargo is absent, the job bootstraps Rustup using its official TLS
installer. It then installs the pinned Rust 1.85.1 toolchain and `cross` 0.2.5.
`cross` uses Docker to build both musl targets; no amd64 or arm64 build host is
required. Do not expose the Docker daemon over an unauthenticated TCP socket.
Rust and Cargo are not required on the runner. Buildx runs the pinned official
`rust:1.85.1-alpine3.21` image natively for amd64 and through QEMU for arm64.
Both resulting binaries are statically linked against musl. No amd64 or arm64
build host is required. Do not expose the Docker daemon over an unauthenticated
TCP socket.
The simplest setup is a dedicated runner VM with an `ubuntu-latest:host` label.
If jobs run inside a container instead, that container needs the Docker CLI and