GitHub runner

  • Canonical IS DevOps
Channel Revision Published Runs on
latest/stable 273 07 Oct 2024
Ubuntu 22.04 Ubuntu 20.04
latest/stable 274 25 Sep 2024
Ubuntu 22.04 Ubuntu 20.04
latest/stable 1 09 Feb 2022
Ubuntu 22.04 Ubuntu 20.04
latest/beta 282 10 Oct 2024
Ubuntu 22.04
latest/beta 234 05 Aug 2024
Ubuntu 22.04
latest/edge 285 Yesterday
Ubuntu 22.04 Ubuntu 20.04
latest/edge 283 10 Oct 2024
Ubuntu 22.04 Ubuntu 20.04
latest/edge 4 26 Apr 2022
Ubuntu 22.04 Ubuntu 20.04
1/stable 177 05 Jun 2024
Ubuntu 22.04
1/edge 177 05 Jun 2024
Ubuntu 22.04
juju deploy github-runner --channel 1/stable
Show information

Platform:

Ubuntu
22.04 20.04

How to deploy on ARM64

The charm supports deployment on ARM64 machines. However, it should be noted that the ARM64 deployment currently only supports ARM64 bare-metal machines due to the limitations of nested virtualization on ARM64.

The following uses AWS’s m7g.metal instance to deploy the GitHub Runner on ARM64 architecture.

Requirements

  1. Juju with ARM64 bare metal instance availability.
    • On AWS: juju bootstrap aws <desired-controller-name>
  2. GitHub Personal Access Token
  3. Repository to register the GitHub runners.

Deployment steps

Run the following command:

juju deploy github-runner \
    --constraints="instance-type=a1.metal arch=arm64" \
    --config token=<PERSONAL-ACCESS-TOKEN> --config path=<OWNER/REPO>

The units may take several minutes to settle. Furthermore, due to charm restart (kernel update), the Unit may become lost for a few minutes. This is an expected behavior and the unit should automatically re-register itself onto the Juju controller after a successful reboot.

Go to the repository > Settings (tab) > Actions (left menu dropdown) > Runners and verify that the runner has successfully registered and is online.