GitHub runner
- By Canonical IS DevOps
| Channel | Revision | Published | Runs on |
|---|---|---|---|
| latest/stable | 256 | 11 Sep 2024 | |
| latest/stable | 244 | 27 Aug 2024 | |
| latest/stable | 1 | 09 Feb 2022 | |
| latest/beta | 257 | 12 Sep 2024 | |
| latest/beta | 234 | 05 Aug 2024 | |
| latest/edge | 263 | Today | |
| latest/edge | 262 | 13 Sep 2024 | |
| latest/edge | 4 | 26 Apr 2022 | |
| 1/stable | 177 | 05 Jun 2024 | |
| 1/edge | 177 | 05 Jun 2024 |
juju deploy github-runner --channel 1/edge
Deploy universal operators easily with Juju, the Universal Operator Lifecycle Manager.
Platform:
ARM64
Nested virtualiztion support
GitHub runner uses LXD to create a virtual machine to run the GitHub runner’s binary. Some versions of the ARM64 architecture do not support nested virtualizations.
Furthermore LXD by default uses QEMU with KVM acceleration options and such behavior cannot overridden. When run on a machine without KVM support, the following error will occur:
Error: Failed instance creation: Failed creating instance record: Instance type "virtual-machine"
is not supported on this server: KVM support is missing (no /dev/kvm)
The kernel for nested virtualizations have not yet landed upstream.
The current progress of ARM64 nested virtualization support requires a few underlying technologies to be further developed.
- Hardware: supported
- Kernel (KVM): upstream not yet ready
- Userspace programs (e.g. qemu): unsupported.
Therefore, it is currently necessary that the charm is deployed on a bare metal instance.