GitHub Actions now supports production-ready Red Hat Enterprise Linux 9 and 10 images on GitHub-hosted larger runners.

GitHub Actions RHEL runners are now generally available, allowing engineering teams to build and test software using Red Hat Enterprise Linux 9 and 10 on GitHub-hosted larger runners.
GitHub confirmed general availability on November 19, 2026, following a public preview introduced in June in partnership with Red Hat. The images are available for Linux x64 larger runners on GitHub Team and GitHub Enterprise Cloud plans.
GitHub Changelog
The update addresses a longstanding CI/CD challenge: software is frequently built and tested on one Linux distribution before being deployed on another.
For applications running on Red Hat Enterprise Linux, that difference can introduce unexpected dependencies, library incompatibilities, packaging issues and deployment failures.
Using RHEL directly in the CI environment allows developers to test against an operating system closer to their production target.
However, general availability does not mean every GitHub Actions workflow automatically switches to RHEL. Organizations must configure the appropriate larger runner, select the operating system image and direct their workflows to the new runner.
What Changed With GitHub Actions RHEL Runners?
GitHub’s November 19 announcement confirms that Red Hat Enterprise Linux 9 and RHEL 10 images have moved from public preview to general availability.
The release makes both images fully supported for production workflows using GitHub-hosted larger runners.
| Feature | Availability |
|---|---|
| Red Hat Enterprise Linux 9 | Generally available |
| Red Hat Enterprise Linux 10 | Generally available |
| Runner architecture | Linux x64 |
| Runner type | GitHub-hosted larger runners |
| Supported plans | GitHub Team and GitHub Enterprise Cloud |
| Existing preview runners | Continue working without migration |
| Custom images | RHEL images can serve as a foundation |
GitHub explicitly states that organizations already using these images during the preview do not need to take action. Existing runners and workflows continue operating.
This reduces migration overhead for early adopters while allowing other organizations to begin using the images through supported production configurations.
Why RHEL 9 and RHEL 10 both matter
Enterprise environments do not necessarily move to a new operating system release immediately.
Some applications may remain on RHEL 9 because of validated dependencies, vendor support requirements or deployment schedules.
Others may target RHEL 10 for newer infrastructure.
Supporting both versions allows teams to test against the operating system release appropriate to their applications rather than relying on a generic Linux environment.
Why Matching CI and Production Operating Systems Matters
Linux distributions share a common kernel architecture, but their user-space environments can differ significantly.
Applications may depend on specific system libraries, package versions, security policies or runtime configurations.
A build that succeeds on Ubuntu does not automatically prove that the resulting software will run correctly on RHEL.
Package and dependency compatibility
Red Hat Enterprise Linux uses RPM-based package management.
A CI workflow designed around Debian or Ubuntu may rely on apt, while a RHEL environment generally uses dnf.
That difference can affect dependency installation, package naming and build scripts.
For example, a workflow that assumes the availability of a particular development library may fail when moved to RHEL because the package has a different name or is provided through a different repository.
Running CI directly on RHEL can expose these issues before deployment.
Runtime and library compatibility
Compiled applications may depend on shared libraries or runtime versions available in the build environment.
Differences in libraries, compiler toolchains or operating system configuration can cause failures that do not appear during development.
Testing on the intended operating system helps identify such problems earlier.
It does not guarantee complete production equivalence, however.
Production infrastructure may still differ in kernel configuration, networking, storage, security policy and installed packages.
How to Configure GitHub Actions RHEL Runners
GitHub’s official larger-runner documentation explains how organization administrators create and manage GitHub-hosted larger runners.
GitHub Docs
The process begins in the organization’s settings.
Step 1: Create a new larger runner
Navigate to the organization on GitHub and open Settings → Actions → Runners.
Select New runner, followed by New GitHub-hosted runner.
Choose Linux x64 as the platform.
Under the available images, select the Partner category and choose the appropriate Red Hat Enterprise Linux image.
Then select the required hardware configuration, maximum concurrency and runner group.
Step 2: Configure repository access
GitHub uses runner groups to control which repositories can access larger runners.
Organization administrators can restrict access to selected repositories rather than exposing the runner to every project.
This is particularly useful when different teams require different operating system versions, network configurations or security policies.
Step 3: Reference the runner in a workflow
After creating the runner, GitHub provides a runner name that can be referenced in workflow configuration.
A minimal example looks like this:
name: RHEL CI Validation
on:
push:
pull_request:
jobs:
validate:
runs-on: YOUR_RHEL_RUNNER_NAME
steps:
- name: Check operating system
run: |
cat /etc/os-release
uname -m
- name: Inspect package manager
run: dnf --version
- name: Run project tests
run: |
echo "Replace with your build and test commands"
Replace YOUR_RHEL_RUNNER_NAME with the actual configured runner label.
This is an illustrative workflow, not a tested production configuration. Teams should add the appropriate checkout action, dependencies, build commands and test procedures for their projects.
GitHub Actions RHEL Runners vs. Standard Ubuntu Runners
GitHub’s standard Ubuntu runners remain useful for many software projects.
They are widely supported and suitable for applications that do not require a specific enterprise Linux distribution.
RHEL runners serve a different purpose: aligning the CI environment with applications that must run on Red Hat Enterprise Linux.
| Consideration | Ubuntu runner | RHEL larger runner |
|---|---|---|
| Primary environment | Ubuntu Linux | RHEL 9 or 10 |
| Package management | APT | DNF/RPM |
| Typical use | General-purpose CI | RHEL-targeted validation |
| GitHub-hosted availability | Standard runner options | Larger runner configuration |
| Production alignment | Depends on target environment | Stronger for RHEL deployments |
The choice should be driven by technical requirements rather than assuming that one Linux distribution is universally better.
For projects deployed on several distributions, a test matrix may be more appropriate than selecting a single runner environment.
Custom RHEL Images for Repeatable CI/CD
GitHub’s announcement also confirms that RHEL images can serve as the foundation for custom images.
This matters for organizations whose builds require specialized toolchains, internal dependencies or standardized configurations.
Instead of installing every dependency from scratch during each workflow, teams can prepare an approved base image.
That image might include supported compilers, build tools, security utilities and other dependencies required by the application.
GitHub documents the relevant process in its custom images guidance.
Why custom images can improve consistency
A standardized image can reduce differences between development teams and CI pipelines.
It can also make environment changes more deliberate.
However, preinstalled dependencies must still be maintained.
A custom image that is not regularly updated may accumulate outdated libraries and security vulnerabilities.
Organizations should therefore version their images, document their contents and establish a process for rebuilding and validating them.
Security Considerations for RHEL-Based CI/CD
Moving to a production-aligned operating system does not automatically make a pipeline secure.
GitHub Actions workflows may execute code from pull requests, download dependencies and access credentials.
The permissions assigned to those workflows remain important regardless of the operating system.
Restrict runner access
GitHub’s documentation allows administrators to control larger-runner access through runner groups.
For sensitive workflows, access should be restricted to the repositories that actually need the environment.
GitHub also warns that untrusted pull-request code can create risks when runners have privileged network access or fixed IP configurations.
Protect deployment credentials
Build and test workflows should not receive production credentials unless those credentials are genuinely required.
Use narrowly scoped permissions and separate untrusted code validation from privileged deployment jobs.
TechnologyHQ’s existing article on GitHub Actions workflow-log secret scanning examines another important aspect of CI/CD security: credentials accidentally exposed through build output.
RHEL runner adoption should preserve these existing protections.
Keep runner images updated
A production-aligned operating system still requires patch management.
Security updates, package repositories and third-party build tools should be reviewed regularly.
For custom images, organizations should maintain a documented rebuild schedule and verify that security patches do not break critical workflows.
How RHEL Runners Affect Enterprise Linux Testing
The main engineering advantage is improved environmental consistency.
For example, an organization deploying a Java application to RHEL 9 can validate its build and integration tests on the same major operating system release.
A team distributing RPM packages can test installation and package dependencies on an appropriate RHEL environment.
A systems-software project can check compiler and library compatibility before producing release artifacts.
These are potential use cases rather than measured performance improvements claimed by GitHub.
CI parity is not complete production parity
Even when the operating system matches, the runner may not reproduce every aspect of production.
A GitHub-hosted runner may differ in available hardware, network topology, security modules, kernel configuration or connected services.
Teams should distinguish operating system compatibility tests from full deployment validation.
For critical systems, staging environments and production-like integration tests remain valuable.
RHEL Runners and GitHub Actions Architecture Changes
The RHEL announcement also highlights why runner architecture matters.
The new RHEL images are specifically available for Linux x64 larger runners.
They should not be confused with ARM64 or legacy ARM32 execution environments.
TechnologyHQ recently examined the GitHub Actions ARM32 support retirement, scheduled for December 8, 2026.
That change affects native 32-bit ARM execution on GitHub-hosted runners.
The new RHEL x64 images do not provide a direct replacement for ARM32 workflows.
Organizations should evaluate operating system version and processor architecture as separate compatibility requirements.
Performance and Cost Considerations
Larger runners offer configurable hardware capacity, but organizations should not assume that RHEL automatically produces faster builds.
Build performance depends on processor allocation, memory, storage, dependencies, caching and the workload itself.
GitHub’s November 19 announcement does not provide comparative benchmarks showing RHEL runners outperforming Ubuntu runners.
It also does not establish a universal fixed price for every RHEL runner configuration.
Teams should consult the current GitHub Actions billing documentation and evaluate the selected runner size and expected job duration.
Measure before standardizing
A practical pilot should compare representative workflows under controlled conditions.
Measure build duration, test success rates, dependency installation time and environment-related failures.
If RHEL alignment eliminates compatibility problems, that benefit may be more valuable than a small difference in raw execution speed.
The goal is reliable software delivery, not merely a faster CI dashboard.
Recommended Migration Strategy for Engineering Teams
Organizations should begin with applications that already deploy to RHEL.
Select a small number of representative repositories and create an appropriately configured larger runner.
Run the existing build and test process on RHEL alongside the current CI environment.
Compare results, identify distribution-specific dependencies and document any required changes.
Once the workflow is stable, consider whether a custom image would improve repeatability.
Deployment checklist
-
Confirm GitHub Team or GitHub Enterprise Cloud eligibility.
-
Choose RHEL 9 or RHEL 10 based on the production target.
-
Create a Linux x64 larger runner using the appropriate Partner image.
-
Restrict repository access through runner groups.
-
Validate package installation, build tools and application tests.
-
Compare CI results with the existing environment.
-
Review runner permissions, secrets and billing.
-
Establish ongoing image maintenance and patching procedures.
A phased rollout makes compatibility problems easier to diagnose and reduces disruption to established development pipelines.
What General Availability Does Not Mean
The November 19 release confirms production support for RHEL 9 and RHEL 10 images on the specified GitHub-hosted larger runners.
It does not mean RHEL is now the default operating system for GitHub Actions.
It does not establish availability on every runner architecture or subscription plan.
It does not guarantee that applications built on RHEL will behave identically in every production deployment.
Nor does it provide independent performance benchmarks or quantified reliability improvements.
These distinctions are important when evaluating the release for enterprise CI/CD architecture.
Frequently Asked Questions
Are GitHub Actions RHEL runners generally available?
Yes. GitHub announced general availability of RHEL 9 and RHEL 10 images for GitHub-hosted larger runners on November 19, 2026.
Which GitHub plans support RHEL larger runners?
GitHub Team and GitHub Enterprise Cloud.
Do existing preview users need to migrate?
No. GitHub says existing RHEL runners and workflows continue working without changes.
Can RHEL runners use custom images?
Yes. GitHub supports using the RHEL images as a foundation for custom runner images.
Are RHEL runners available for ARM64?
The November announcement specifies Linux x64 larger runners. It does not establish RHEL image availability for ARM64.
Do RHEL runners replace Ubuntu runners?
No. They provide an additional operating system option for workloads that benefit from RHEL compatibility.
Will RHEL runners make builds faster?
Not necessarily. Performance depends on runner resources and workload characteristics. GitHub did not publish a universal performance comparison in the announcement.
The Bottom Line
The general availability of GitHub Actions RHEL runners is a useful development for organizations building and deploying software on Red Hat Enterprise Linux.
Supporting RHEL 9 and RHEL 10 on GitHub-hosted larger runners makes it easier to align CI environments with production operating systems and test distribution-specific dependencies before deployment.
The strongest benefit is not a promised increase in raw performance. It is the opportunity to identify compatibility problems earlier and maintain more consistent build environments.
Engineering teams should evaluate the new images through controlled pilots, preserve existing security controls and select runner configurations based on their actual deployment requirements.

Ingrid Maldine is a business writer, editor and management consultant with extensive experience writing and consulting for both start-ups and long established companies. She has ten years management and leadership experience gained at BSkyB in London and Viva Travel Guides in Quito, Ecuador, giving her a depth of insight into innovation in international business. With an MBA from the University of Hull and many years of experience running her own business consultancy, Ingrid’s background allows her to connect with a diverse range of clients, including cutting edge technology and web-based start-ups but also multinationals in need of assistance. Ingrid has played a defining role in shaping organizational strategy for a wide range of different organizations, including for-profit, NGOs and charities. Ingrid has also served on the Board of Directors for the South American Explorers Club in Quito, Ecuador.






























