A GitHub Actions pipeline successfully builds and tests RHEL 9 and 10 in a secure cloud environment.
GitHub has moved its Red Hat Enterprise Linux images for Actions out of preview. Runner images for both RHEL 9 and RHEL 10 are now generally available. GitHub's changelog posted the news on November 19, 2026. Teams that keep CI on Red Hat can now use a hosted runner instead of running their own fleet.

A GitHub Actions pipeline successfully builds and tests RHEL 9 and 10 in a secure cloud environment. What changed​

GitHub says the RHEL 9 and RHEL 10 images for GitHub-hosted larger runners are fully supported for production workflows in GitHub Actions. They first appeared as a public preview on June 25, 2026, in partnership with Red Hat.

GitHub gives two uses for the images:

  • Run workflows on the same operating system you deploy to.
  • Use the image as the base for a custom image that carries your own tools, dependencies and configuration.

If you used the preview, you don't need to do anything. GitHub says your existing runners and workflows keep working as they are. It announced no migration, no change to workflow syntax and no breaking change.

Who can use it​

GA does not mean everyone gets it. The boundaries are:

  • Runner type: Linux x64 larger runners only. These are not the standard ubuntu-latest-style runners.
  • Plans: GitHub Team and GitHub Enterprise Cloud. GitHub's docs say larger runners in general are limited to organizations and enterprises on those plans.
  • Account type: Larger runners need an organization or enterprise. Red Hat's preview post said individual accounts weren't supported in the preview, and I found no GA statement that changes this.

Red Hat's GA post also mentions GitHub Enterprise Server. GitHub's changelog names only Team and Enterprise Cloud. I wouldn't assume Enterprise Server support without checking GitHub's documentation.

How to set it up​

  1. In your organization, go to the larger runner creation flow. Red Hat's GA post gives the path as Settings → Actions → Runners → New larger runner.
  2. Choose Linux x64 as the platform.
  3. Pick RHEL 9 or RHEL 10 under Partner images.
  4. Choose a size. GitHub's docs say the available sizes depend on the image you select. The sources don't say which sizes RHEL supports, so check the list in the UI.
  5. Set the maximum concurrency and the runner group. Choose networking settings too if you need them.
  6. Create the runner.

GitHub's announcement doesn't give a specific runs-on label for these images. Don't guess one. Use the name of the runner you create, as you would with any other larger runner.

Partner images are not GitHub-maintained images​

GitHub's larger-runner reference separates GitHub-owned images from partner images. Red Hat's GA post says the RHEL runners come straight from base Azure Marketplace VM images, so they are minimal base operating systems without the gigabytes of preinstalled tools on other GitHub runners.

That affects planning in three ways:

  • Tooling: Don't expect the toolchain you get on ubuntu-latest. Plan to install what you need, or bake it into a custom image.
  • Image changes: GitHub's docs say only GitHub-owned images can be swapped on an existing runner. If you want to move between RHEL versions, expect to create a new runner. The docs don't spell this out for partner images, so treat it as my reading.
  • Issue reporting: GitHub's reference says partner images aren't managed by GitHub and points to separate resources for reporting problems. Find the right channel before something breaks.

Custom images on a RHEL base​

Because the RHEL image is minimal, a custom image is probably how most teams will use it. GitHub's custom-image documentation describes the process:

  1. Set up an image-generation runner. The platform must match the image you want to build. Select the base image and tick Enable this runner to generate custom images.
  2. Run a workflow with the snapshot keyword on that runner. Each successful job that includes snapshot creates a new image version.
  3. Create a runner that uses the custom image. Pick it from the Custom tab, and choose a size with storage at least as large as the image.

Details from the docs that matter in practice:

  • Custom images must be enabled in your organization or enterprise policy. You need to be an owner, have the CI/CD Admin role, or hold specific fine-grained permissions.
  • GitHub recommends regenerating the image on a weekly schedule so dependencies stay patched.
  • Provisioning can take several hours, depending on runner size and configuration.
  • Jobs on custom images are billed at the same per-minute rate as the larger runner. Image storage is billed separately through Actions storage, and it can grow quickly if you keep many versions.
  • Keep image-generation runners in a dedicated runner group. Don't let public repositories use them, and limit write access. Anyone who can run a workflow on that runner could put malicious code into an image.

Why teams want it​

Red Hat's preview post made the case plainly. Most GitHub-hosted runners use Linux, but not a RHEL distribution, and that mismatch brings different package versions, defaults, performance characteristics and security behaviors. One CI/CD trade publication said the preview suited shops that had been self-hosting Actions only to keep production-like CI on Red Hat. That is an outside opinion, not a GitHub claim.

Running tests on RHEL 9 or 10 should surface package, library and default-configuration differences earlier. It won't remove every difference between CI and production. Kernel settings, hardware, network layout, installed packages and subscription or repository configuration can still differ. GitHub's announcement doesn't claim otherwise.

A hosted RHEL runner also removes some operational work. You no longer have to patch and scale your own pool just to get a RHEL host. You do give up some control compared with a self-hosted runner. That matters if you need unusual host settings or private network access. Larger runners support Azure private networking and static IPs on Linux. The sources don't confirm that every such option works with the RHEL images, so check before you depend on one.

Cost​

Larger runners are billed per minute only while jobs are running. GitHub's docs say there's no charge for a configured runner that sits idle. Included compute on Team and Enterprise Cloud accounts may offset some of the cost. Usage in public repositories is billed at the per-minute rate.

The sources give no RHEL-specific rate, so check GitHub's Actions runner pricing page before you commit a large pipeline.

Troubleshooting​

GitHub's larger-runner troubleshooting notes cover the usual causes when jobs are delayed or never start:

  • Concurrency limit: you've hit the maximum you configured. Raise it in the runner's autoscaling settings.
  • Repository access: enterprise runners are not available at the repository level by default. An organization admin has to enable them.
  • Billing: a valid payment method must be on file, and it can take up to 10 minutes to activate after you add one.
  • Spending limit: it must be set above zero.
  • Cold start: larger runner pools are smaller than standard ones, so the first job may wait while GitHub creates a VM.

Bottom line​

This is a modest but useful change for enterprise Linux shops. RHEL 9 and 10 are now supported for production on GitHub-hosted larger runners, and nothing breaks for preview users. Check that you're on a Team or Enterprise Cloud plan, and expect to build a custom image to get a working toolchain. GitHub hasn't published image inventories, RHEL minor-version details, or image-specific size, security and support boundaries.

 

References

  1. Red Hat Enterprise Linux runner images now generally available GitHub Changelog 2026-11-19T18:48:46+00:00
  2. Managing larger runners - GitHub Enterprise Cloud Docs docs.github.com
  3. Larger runners reference - GitHub Docs docs.github.com