actions / actions/actions-runner-controller
Reconsider Aligning `actions-runner` software with Github-hosted software
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 6.5k
- Forks
- 1.5k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 27
Description
What would you like added?
I would like the existing images without Cloud-specific tooling to be appended with i.e. -slim or -cloudless , and for the default actions-runner images to have the same installed software as their related actions/runner-images images
Why is this needed?
Now that Actions Runner Controller has been officially adopted into the actions/ org I think it is worth reconsidering alignment of pre-installed software with actions/runner-images.
ARC's end users are often unaware that ARC is being used and expect consistent pre-installed software when developing their workflows. When ARC runners are provided to supplement or replace Github-hosted runners, errors are likely to occur due to the delta between preinstalled software on Github-hosted runners and ARC-hosted runners.
While some end-user friction can be mitigated by an organization's ARC operators, they may not have insight into all tooling required by end users across the org, leading to increased friction for ARC adoption. Sourcing the same software as actions/runner-images reduces that friction significantly.
Additional context
Installed Software for actions/runner-images
ubuntu-latest or ubuntu-22.04
ubuntu-20.04
I'm happy to help with the lift on this, but I wanted to float it in the community first for feedback
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing the existing ARC runner images with the linked actions/runner-images Ubuntu 22.04 and 20.04 software lists. Define the scope for cloudless image naming and software alignment, then review the community feedback before proposing changes. Done means the desired image variants and installed-software parity are clearly specified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, kubernetes
- Domain
- ci-cd, devops, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100