-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Showing feature comparison between self-hosted runners #9325
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from 3 commits
265ee00
6e838e4
47491d3
d2dae77
6db4cf9
97e71e2
96738e1
9213113
17b6671
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,121 @@ | ||
| --- | ||
| contentTags: | ||
| platform: | ||
| - Cloud | ||
| - Server v4+ | ||
| --- | ||
| = Self-hosted runner feature comparison | ||
| :description: A comparison table of the features available for CircleCI runners. | ||
| :page-layout: classic-docs | ||
| :page-liquid: | ||
| :icons: font | ||
| :experimental: | ||
|
|
||
| This page offers a comparison of the features available for CircleCI Machine runner vs. CircleCI Container Runner. | ||
|
|
||
| [#feature-comparison-matrix] | ||
| == Comparison matrix | ||
|
|
||
| [.table.table-striped] | ||
| [cols=4*, options="header", stripes=even] | ||
| |=== | ||
| |Feature | ||
| |Description | ||
| |Machine Runner | ||
| |Container Runner | ||
|
|
||
| |*Environment* | ||
| |Where jobs run and how resources are managed | ||
| |Full VM/bare metal | ||
| |Kubernetes Pods | ||
|
|
||
| |*Configuration File* | ||
| |Primary file for runner setup | ||
| |YAML config (location depends on OS) | ||
| |Helm `values.yaml` | ||
|
|
||
| |*Resource Control* | ||
| |How compute resources are allocated | ||
| |System level | ||
yaningo marked this conversation as resolved.
Show resolved
Hide resolved
|
||
| |Kubernetes limits | ||
|
|
||
| |*Architecture Support* | ||
| |CPU architectures available for builds | ||
| |Not specified | ||
yaningo marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
| |AMD64/ARM64 with `nodeSelector` | ||
|
|
||
| |*Job Isolation* | ||
| |How jobs are kept separate | ||
| |VM-level | ||
| |Container-level | ||
|
|
||
| |*Scaling* | ||
| |How runner capacity scales with demand | ||
| |Manual/custom | ||
yaningo marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
| |Kubernetes-based auto-scaling | ||
|
|
||
| |*Service Containers* | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Is this configuring more than one vm/container for a job? Is this definitely not supported for machine runners? |
||
| |Support for additional services in build | ||
| |Not supported | ||
| |Extensive support with resource controls | ||
|
|
||
| |*Execution Modes* | ||
| |How runner handles job execution | ||
| |`single-task` or `continuous` | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I'm sure these are defined somewhere in the runner docs, maybe we can add a link? |
||
| |Pod-based execution | ||
|
|
||
| |*Docker Support* | ||
| |How Docker-in-Docker is handled | ||
| |Native OS support | ||
| |Requires special configuration (`setup_remote_docker`) | ||
|
||
|
|
||
| |*Resource Cleanup* | ||
| |How build environments are cleaned after jobs | ||
| |Working directory cleanup | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Link to docs that covers this if this exists? |
||
| |Container lifecycle | ||
| |=== | ||
|
|
||
|
|
||
| [#feature-highlights] | ||
| == Feature Highlights | ||
|
|
||
| *Machine Runner* | ||
|
|
||
| * Latest generation of machine-based runners | ||
yaningo marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
| * Full access to underlying operating system | ||
| * Ideal for workflows requiring VM-level isolation | ||
| * Consistent environment variables with `CIRCLECI_RUNNER_*` prefix | ||
yaningo marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
| * Supports SSH connectivity for debugging | ||
|
|
||
| *Container Runner* | ||
|
|
||
| * Kubernetes-native solution for container-based workflows | ||
| * Fine-grained resource allocation and constraints | ||
| * Supports service container configurations with pattern matching: | ||
yaningo marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
| * Advanced node selection via Kubernetes annotations | ||
| * Custom security contexts and volume mounting | ||
| * Support for spot instances via tolerations | ||
| * Configurable resource limits for primary and service containers | ||
|
|
||
|
|
||
| [#key-differences] | ||
| == Key Differences | ||
|
|
||
| *Machine Runner* offers full VM isolation with the newest | ||
| configuration patterns and improved controls. | ||
|
|
||
| *Container Runner* leverages Kubernetes for: | ||
|
|
||
| * Container-based isolation | ||
| * Better scaling capabilities | ||
| * Advanced resource management | ||
| * Multiple architecture support | ||
|
|
||
| [#choose-a-runner] | ||
| == When to Choose Each Runner | ||
|
|
||
| *Machine Runner*: Choose for full system access, custom system | ||
| dependencies, or when Kubernetes isn’t available. | ||
yaningo marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
|
|
||
| *Container Runner*: Best for cloud-native applications, teams using | ||
| Kubernetes, and workloads that benefit from container orchestration. | ||
Uh oh!
There was an error while loading. Please reload this page.