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:
SSH Debug
SSH debugging allows a user to identify and resolve issues or errors that occur through the secure shell (SSH) connection between a client and a server.
To enhance the security of the runner and the infrastructure behind the runner, only user ssh-keys registered on Authorized Keys are allowed by default on tmate-ssh-server charm.
Authorized keys are registered via action-tmate’s
limit-access-to-actor
feature. This feature uses GitHub users’s SSH key to launch an instance
of tmate session with -a
option, which adds the user’s SSH key to ~/.ssh/authorized_keys
.
Firewall rules
By default, if there are any overlapping IPs within the denylist
config option with the IP
assigned to tmate-ssh-server
, an exception to that IP will be made so that the debug-ssh
relation can be set up correctly.