Modern software teams build code faster than ever. But building code faster creates a major roadblock when checking whether that code works.
Both human code and AI-generated code cause problems if you lack a reliable test environment. When fast coding meets complex deployment setups, fixing broken pipelines by hand slows teams down. One problem you need to avoid is running automated tests on one Linux distribution when you deploy to another in production.
When you build applications for Red Hat Enterprise Linux (RHEL), testing on other systems creates risk. Few things frustrate a team more than passing every test on non-RHEL runner images, only to watch the build crash in staging.
These failures happen because of small differences in shared libraries (such as glibc), device driver behaviors, or stricter SELinux rules in production environments. Different compiler settings, library versions, and security rules let hidden bugs slip past tests. Developers then spend hours writing custom scripts to bridge those gaps.
This is why official GitHub-hosted runners for RHEL matter. Runner images for both RHEL 9 and RHEL 10 are now generally available.
Software development teams using GitHub Enterprise Cloud and GitHub Enterprise Server can now run continuous integration and continuous delivery (CI/CD) pipelines directly on native RHEL environments.
How to try it
These runners are clean base operating system images running on 64-bit Linux. You add the tools and applications your project needs on top. You can set up a runner in your GitHub organization in 3 steps:
- Create a larger runner: Go to your organization settings in GitHub. Navigate to Settings → Actions → Runners → New larger runner. Larger runners require a GitHub organization account.
- Pick your system image: Under the Linux x64 runner options, choose Linux x64 partner images. Select either RHEL 9 or RHEL 10 based on your project needs.
- Point your workflow to your runner: Give your runner a group label, such as
your-runner-group-label. Add that label to your workflow file so GitHub knows where to run your job.
The following example shows a basic workflow setup:
jobs:
build:
runs-on: [self-hosted, your-runner-group-label]
steps:
- name: Verify System
run: cat /etc/redhat-releaseConfigure a container host
Small cloud images help reduce security risks and keep systems clean. Because GitHub Actions partner runner images for RHEL come straight from base Azure Marketplace virtual machine images, they are minimal base operating systems. They don't include the gigabytes of preinstalled tools found on other runners provided by GitHub.
This means neither Git tools nor Podman come preinstalled. You might not need them for every job, but most container workflows require both. Teams can install them using dnf during workflow setup or save them into a custom larger runner image.
Do you need to manage license keys to install packages? No. These cloud images connect directly to cloud update mirrors. You can install tools right away without entering registration keys into your repository secrets.
To build containers, replace the previous example with this complete job definition:
name: RHEL Container Delivery
on:
push:
branches: [ "main" ]
pull_request:
branches: [ "main" ]
jobs:
build:
runs-on: [self-hosted, your-runner-group-label]
steps:
- name: Install Git Tools and Container Suite
run: |
echo "=== Provisioning Pipeline Toolchains ==="
# container-tools provides Podman, Buildah, Skopeo, and runc
sudo dnf -y install git container-tools
git --version
podman --version
- name: Checkout Source Code
uses: actions/checkout@v4
- name: Verify Container Environment
run: |
echo "=== Operating System Information ==="
cat /etc/redhat-release
podman info
- name: Build Application Container
run: |
# Podman runs safely in rootless mode on native RHEL runners
podman build -t enterprise-app:latest .To speed up frequent use of common custom images, GitHub recommends its custom image feature. You can use it to cut the time involved with installing extra packages.
Choose your environment: RHEL 9 stability or RHEL 10 innovation
Native runners give teams the choice to test on stable production standards or try modern platform features within the exact same pipeline:
- RHEL 9 runner: Recommended for existing applications that need long-term stability. This image includes proven compiler baselines, stable Python versions, and long-term maintenance system libraries.
- RHEL 10 runner: Recommended for new cloud projects, modern microservices, and AI applications. This image includes modern GNU Compiler Collection (GCC) 14, Python 3.12, and tools built for image mode for Red Hat Enterprise Linux.
Addressing core delivery challenges
Native runner images help resolve common pipeline problems before they reach production:
- Fewer library mismatches: Testing directly on RHEL helps verify your application links against the exact same C libraries used on your production servers.
- No security rule surprises: Testing under native policies catches SELinux permission denials during automated tests rather than during deployment.
- Predictable container behavior: Building with Podman on native runners helps verify container permissions, user IDs, and storage drivers behave the same way in CI as they do on host clusters.
Quality and security validation checkpoints
By testing builds across multiple RHEL versions, engineering teams catch platform-specific issues and retired features early in pull request reviews:
- Build checks: Compiling code on native RHEL runners catches missing system libraries and compiler flag differences before code merges.
- Container security: Running container builds with Podman confirms applications run safely without requiring root privileges.
- Version checks: Testing workloads across both RHEL 9 and RHEL 10 flags deprecated packages before production systems undergo platform upgrades.
Align your workstation with your automation
When your local workstation mirrors your CI runner, you catch platform-specific issues before pushing code. Testing locally with the same tools used in your pipeline saves hours of troubleshooting failed remote builds.
Start building on Red Hat Enterprise Linux runners today
To get the most out of your new Red Hat Enterprise Linux workflow, you need a local development environment that matches your CI pipeline. The Red Hat Developer program makes this easy. A no-cost membership includes:
- No-cost subscriptions: Developers can obtain full self-service access to Red Hat Enterprise Linux for individual or business development use.
- Local development tools: Developers can download the Red Hat build of Podman Desktop to build and manage containerized workloads locally before pushing them to GitHub with the GitHub plug-in.
- Full supply chain bits: Developers have full access to supported Red Hat container images including Red Hat Hardened Images and Red Hat Universal Base Images (UBI).
Ready to eliminate environment drift in your enterprise application development pipelines? Update your workflow YAML file to use runs-on: rhel-9 or runs-on: rhel-10. For matching local tooling, sign up for a no-cost Red Hat Developer account today to run the same environment on your workstation as in your GitHub-hosted runners.