docs: full apply command for the proposed host runner
Refs #45 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
@@ -205,7 +205,8 @@ I3 and S3: run the runner on `inspiron-3670` instead of in the cluster.
|
|||||||
variables as the in-cluster runner. Host-only ones are `gitea_actions_host_*`
|
variables as the in-cluster runner. Host-only ones are `gitea_actions_host_*`
|
||||||
in the role's `defaults/main.yml`: 4 CPUs and 16 GB for jobs, and a CPU
|
in the role's `defaults/main.yml`: 4 CPUs and 16 GB for jobs, and a CPU
|
||||||
weight below the host's other containers.
|
weight below the host's other containers.
|
||||||
- **Apply.** `ansible-playbook ci-runner.yaml`. The first run fetches a
|
- **Apply.** `ansible-playbook -i inventories/eom.dev.yml ci-runner.yaml -K`
|
||||||
|
(`-K` because the host asks for a sudo password). The first run fetches a
|
||||||
registration token from the cluster, registers, and deletes the token file.
|
registration token from the cluster, registers, and deletes the token file.
|
||||||
Rerunning recreates only containers whose settings changed; that cancels a
|
Rerunning recreates only containers whose settings changed; that cancels a
|
||||||
running job.
|
running job.
|
||||||
|
|||||||
Reference in New Issue
Block a user