Commercial CI/CD
Hosted Linux runner guide
Understand hosted access approval, supported images, Docker/Testcontainers boundaries, output collection, and when to use self-hosted capacity.
Launch boundary
Hosted runners are Linux-only. Jobs run in platform-provided images and do not receive the host Docker socket. Docker-capable jobs request a per-job rootless Docker daemon sidecar. The worker host and sidecar model still require real-hardware validation.
Approval model
Hosted access is manually approved before customer workloads run. Use self-hosted runners while access is pending. Terminal hosted assignments use shared run-graph reconciliation; a run remains active only while other materialized/dependent work is unresolved.
When to self-host
Use self-hosted runners for private-network access, custom tooling, deployment CLIs, privileged Docker, custom mounts, or workloads that need unsupported host features. Both runner types deliver organization/pipeline/step/deployment credentials for trusted non-pull-request work and withhold them for pull requests.
Supported images and outputs
The accepted image names are ubuntu-24.04, ubuntu-latest, dotnet-10, node-22, plus Docker-capable variants. Workers collect non-empty files from artifacts/, test-results/, and coverage/ after execution. YAML cache steps save declared directories after successful trusted execution and restore checksum-verified exact/fallback matches before commands.
scripts/validate-hosted-canary.ps1 proves one synthetic assignment, conventional outputs, Docker sidecar reachability, a declared cache archive, and a public service container. It does not prove private checkout, scoped-secret parity, streaming logs, Compose, Buildx, Testcontainers, hostile workload isolation, sustained concurrency, or crash cleanup.