You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
actions/runner — official s390x runner binary builds
Use Case
Organizations running workloads on IBM Z mainframes (s390x architecture) need GitHub Actions self-hosted runners that run natively on s390x to:
Build and test s390x-native applications — Many enterprise workloads (banking, insurance, government) run on IBM Z. CI/CD pipelines need native s390x runners to build, test, and validate these applications.
Avoid emulation overhead — Cross-compilation and QEMU emulation are slow and unreliable for complex test suites.
Support container-native workflows — With ARC on Kubernetes/OpenShift for s390x, organizations can leverage the same ephemeral, auto-scaling runner infrastructure used on amd64/arm64.
Current Workarounds
Today, running ARC on s390x requires:
Custom-building the ARC controller for linux/s390x from upstream source (the Go codebase compiles cleanly for s390x)
Using a community fork (Gold-Bull/github-actions-runner) for s390x runner binaries — this fork is significantly behind upstream (last release: v3.314.1, corresponding to upstream v2.314.1 from March 2024)
Manual Helm value overrides pointing to custom-built images in private registries
What We're Asking For
Short term
Add linux/s390x to the ARC controller's multi-platform container image build matrix. The controller is written in Go and the base image (distroless) supports s390x — this should be a minimal change to the CI/CD pipeline.
Medium term
Publish official linux/s390x runner binaries in actions/runner releases. The .NET runtime (which the runner is built on) has supported s390x since .NET 8.
Evidence of Demand
The Gold-Bull/github-actions-runner community fork has been providing experimental s390x builds since 2022, demonstrating sustained community demand.
IBM Z / LinuxONE serves over 70% of the world's transaction value (banking, payments, government systems). These organizations increasingly adopt GitHub for source control and CI/CD.
Multiple enterprises are independently custom-building ARC for s390x — official support would consolidate effort and improve quality.
Technical Feasibility
Component
s390x Readiness
ARC Controller (Go)
✅ Go supports GOARCH=s390x natively
Controller base image (distroless)
✅ Multi-arch including s390x
Runner (.NET)
✅ .NET 8+ supports linux-s390x
Runner container hooks
✅ Go-based, compiles for s390x
Helm charts
✅ Architecture-agnostic
Willing to Contribute
We are prepared to submit pull requests for adding s390x support to the controller image build pipeline. We have production experience running ARC on s390x (OpenShift on IBM Z) and can provide testing evidence.
Environment
Platform: OpenShift 4.x on IBM Z (s390x)
ARC Version tested: 0.14.2 (custom-built for s390x)
ActionsBuild, test, and automate your deployment pipeline with world-class CI/CDQuestionAsk and answer questions about GitHub features and usageARC (Actions Runner Controller)For issues and discussions related to the Actions Runner Controller projectWelcome 🎉Used to greet and highlight first-time discussion participants. Welcome to the community!source:uiDiscussions created via Community GitHub templates
1 participant
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
🏷️ Discussion Type
Question
💬 Feature/Topic Area
ARC (Actions Runner Controller)
Discussion Details
GitHub Actions Community Discussion Draft
Description
We are requesting official
linux/s390x(IBM Z / LinuxONE) platform support for:Use Case
Organizations running workloads on IBM Z mainframes (s390x architecture) need GitHub Actions self-hosted runners that run natively on s390x to:
Current Workarounds
Today, running ARC on s390x requires:
linux/s390xfrom upstream source (the Go codebase compiles cleanly for s390x)What We're Asking For
Short term
linux/s390xto the ARC controller's multi-platform container image build matrix. The controller is written in Go and the base image (distroless) supports s390x — this should be a minimal change to the CI/CD pipeline.Medium term
linux/s390xrunner binaries in actions/runner releases. The .NET runtime (which the runner is built on) has supported s390x since .NET 8.Evidence of Demand
Technical Feasibility
GOARCH=s390xnativelyWilling to Contribute
We are prepared to submit pull requests for adding s390x support to the controller image build pipeline. We have production experience running ARC on s390x (OpenShift on IBM Z) and can provide testing evidence.
Environment
All reactions