---
title: Charmhub | Deploy GitHub runner using Charmhub - The Open Operator Collection
description: Deploy the latest version of GitHub runner on any cloud.
url: https://charmhub.io/github-runner/docs/reference-external-access
---

# GitHub runner

[Canonical IS DevOps](https://charmhub.io/publisher/canonical-is-devops "View all packages from Canonical IS DevOps")

* [Canonical IS DevOps](https://charmhub.io/publisher/canonical-is-devops "View all packages from Canonical IS DevOps")

Platform:

24.04

22.04

20.04

stable 24801f1f

```
juju deploy github-runner
```

[Learn to deploy on juju >](https://juju.is/docs/juju/manage-applications)

---

#### Contacts

##### Maintainers

+ [Launchpad Team](https://launchpad.net/~canonical-is-devops)

* [Submit a bug](https://github.com/canonical/github-runner-operator/issues)

---

Share your thoughts on this charm with the community on discourse.

[Join the discussion](https://discourse.charmhub.io/)

# External access

The GitHub Runner Charm itself requires access to the

* GitHub API (e.g. to register and remove runners).
* GitHub website (e.g. to download the runner binary or other applications like `yq`)
* Ubuntu package repositories (e.g. to install packages)
* Snap store (e.g. to install LXD or aproxy)
* [Ubuntu Cloud Images](https://cloud-images.ubuntu.com/) (for the image used by a runner)
* NPM registry (e.g. to download and install specific packages)

In addition, access is required depending on the requirements of the workloads that the runners
will be running (as they will be running on the same machine as the charm).

More details on network configuration can be found in the
[charm architecture documentation](https://charmhub.io/github-runner/docs/explanation-charm-architecture).

---