# GitHub Actions

GitHub Actions is a self-hosted automation app. An experimental Docker image that runs self-hosted GitHub Actions runners with Docker support for CI teams whose jobs require containers. It is open source and self-hosted, installable on Docker Hub.

Canonical page: https://ourlocalhost.com/app/5190/github-actions

## Description

An experimental Docker image that runs self-hosted GitHub Actions runners with Docker support for CI teams whose jobs require containers.

## Platform availability

Available on 0 of 10 platforms.

## Links

- Docker Hub: https://hub.docker.com/r/docker/github-actions

## Common questions

### Which GitHub scope settings must be correct before the runner container starts?

Set RUNNER_SCOPE to repo, organization, or enterprise, and provide the matching REPO_URL, ORG_NAME, or ENTERPRISE_NAME. The entrypoint checks these first, so the runner will not start if they are missing or do not match.

### What credential options can register the self-hosted runner with GitHub?

Provide a personal access token, a GitHub App private key, or a pre-created runner token. A valid credential is required to register the runner with GitHub and allow it to pick up jobs.

### How do workflows that need Docker work with this image?

Set START_DOCKER_SERVICE=true when workflows need to build or run containers. Docker is started only when this is enabled, and job steps that use Docker will fail without it.

### How can sensitive deployment data be kept secure for runner workflows?

Store sensitive values in GitHub's encrypted secrets feature rather than exposing them in logs or to unauthorized users.

### How can operators diagnose a self-hosted runner that is not behaving as expected?

Use GitHub's monitoring and troubleshooting capabilities to view runner activity and diagnose common issues.

---
Source: Our Local Host (https://ourlocalhost.com/app/5190/github-actions), the self-hosted and open-source app directory.
