GitHub runner
- Canonical IS DevOps
| Channel | Revision | Published | Runs on |
|---|---|---|---|
| latest/stable | 308 | 11 Dec 2024 | |
| latest/stable | 302 | 02 Dec 2024 | |
| latest/stable | 1 | 09 Feb 2022 | |
| latest/beta | 317 | 11 Dec 2024 | |
| latest/beta | 310 | 28 Nov 2024 | |
| latest/edge | 322 | 20 Dec 2024 | |
| latest/edge | 310 | 28 Nov 2024 | |
| latest/edge | 4 | 26 Apr 2022 | |
| local-lxd/stable | 306 | 17 Dec 2024 | |
| local-lxd/edge | 306 | 27 Nov 2024 | |
| 1/stable | 177 | 05 Jun 2024 | |
| 1/edge | 177 | 05 Jun 2024 |
juju deploy github-runner
Deploy universal operators easily with Juju, the Universal Operator Lifecycle Manager.
Platform:
Managing resource usage
The charm can be hardware intensive, as each instance of self-hosted runner application is hosted in a virtual machine.
Virtual machine resource usage
The minimum requirements for a single virtual machine are:
- 1 virtual machine vCPU
- 2GiB of virtual machine memory
- 10GiB of virtual machine disk
Juju machine resource usage
It is recommended the Juju machine has a minimum of 4GiB of memory dedicated to itself. Generally, 20GiB of disk is provisioned for the Juju machine for the Juju logs.
The Juju machine will also need the enough resources to host the virtual machines.
The recommended combined resource usage is:
- vCPU: Depends on the workload
- memory: number of virtual machines * (memory per virtual machine + disk per virtual machine) + 4GiB
- disk: 20GiB
If memory is used as runner storage:
- memory: number of virtual machines * (memory per virtual machine + disk per virtual machine) + 4GiB
Juju machine constraints
During deployment of the charm, constraints can be used to specify the Juju machine resource requirements. For example, juju deploy github-runner --constraints="cores=4 mem=16G disk=20G".