actions / actions/actions-runner-controller
arm/v7 and arm/v8 variants for runner (not controller) images
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 6.5k
- Forks
- 1.5k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 27
Description
Extracted from https://github.com/actions-runner-controller/actions-runner-controller/pull/1120
Although I don't think it's common to run K8s and ARC on 32bit ARM, it would be still useful to allow runner pods on those arch, like when you run K8s and ARC in a managed K8s cluster and nodes and runner pods on your raspis.
This would require us to migrate our use of dumb-init to an init system that runs of 32bit ARM, e.g. tini.
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 locating the runner image build definitions and the current dumb-init usage. Check how runner images are published for architectures, then evaluate the tini migration for arm/v7 and arm/v8 runner pods. Done means the runner images support those ARM variants and start successfully without changing controller images.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, kubernetes
- Domain
- ci-cd, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100