docker / docker/setup-docker-action
Support for Github ARM Runners
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 77
- Forks
- 22
- Avg merge
- 7d 5h
- Merged PRs (30d)
- 6
Description
We experienced quite some issues when github updated their runners to ship with docker version 29.1.5 (previously was 27/28), so we decided to ensure we have control over which docker version is installed in our workflows. Thus we found this action and at the start everthing was looking great... for AMD64 runners at least.
Once we tried building multi-arch images for one of our projects, we observed very strange errors:
- like
Image with name "..." not found(example) even though the image was just pulled a few seconds earlier
We tried a bunch of workarounds that were discussed here but none seemed to fix our issue - all attempts are also visible here.
Our last idea was to install docker differently... via apt instead of using docker/setup-docker-action. And to our supprise that solved all our issues (this run).
That made us curious: is this action supposed to be working on githubs official arm based runners? (e.g. ubuntu-24.04-arm) and if not, do you plan to add support for arm runners in the near future?
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 reviewing the action's behavior on GitHub's ubuntu-24.04-arm runners and compare it with the linked failing and successful workflow runs. Determine whether ARM runners are supported and identify the changes or tests needed for Docker installation to work there; done means the reported multi-architecture workflow succeeds without the apt workaround.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, github-actions, typescript
- Domain
- ci-cd, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100