GitHub Actions Adds RHEL 9 and 10 Runners: How to Set Them Up

Want your CI to behave more like your production Red Hat server? GitHub Actions now supports Red Hat Enterprise Linux 9 and 10 runner images for production workflows.

GitHub announced general availability on November 19, 2026. The useful part: you can test builds and scripts on RHEL instead of assuming an Ubuntu runner behaves the same way.

What actually changed?

RHEL 9 and RHEL 10 partner images are now generally available for GitHub-hosted larger runners. They were previously in public preview, introduced in June 2026.

  • Choose RHEL 9 or RHEL 10 as your runner’s base operating system.
  • Run CI on an OS closer to your deployment target.
  • Use a RHEL image as the foundation for a custom runner image with your own dependencies.
  • Keep existing preview runners: GitHub says no migration action is required.

How to set it up

You need an organization on GitHub Team or GitHub Enterprise Cloud, plus organization-owner or appropriate enterprise-owner access to manage larger runners.

  1. Open your GitHub organization and go to Settings → Actions → Runners.
  2. Select New runner → New GitHub-hosted runner.
  3. Choose Linux x64 and find the RHEL 9 or RHEL 10 image under Partner images.
  4. Pick a supported machine size, name the runner, set its group and concurrency, then create it.
  5. Confirm the intended repositories can access that runner group before updating workflows to target the configured runner.

Runner labels and group configuration are organization-specific. Don’t paste a guessed runs-on value into production workflows; use the runner name and group configured in your account.

Why developers should care

OS differences matter for system libraries, package managers, shell scripts and dependency versions. Testing on RHEL can reveal issues that an Ubuntu-only CI job might miss, especially when you deploy to RHEL-compatible servers.

Practical takeaway: add a RHEL runner to a noncritical workflow first, compare the results with your existing Linux CI, and migrate only where the extra coverage is useful.

Caveat: these are paid-plan larger runners, not a new free ubuntu-latest replacement. Runner usage may incur additional charges; review your organization’s Actions billing and available machine sizes before enabling broad use.

Sources

Leave a Reply