actions / actions/actions-runner-controller
Add DockerHub credentials such that all action requests to dockerhub are authenticated
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?
A way to add our dockerhub credentials to the action runners such that we won't be rate limited by dockerhub pulls that our github actions perform.
Why is this needed?
We are facing rate limits even after using a dockerhub authentication step in our github action workflows, because we use Docker powered open source actions in our workflows. (This is because container pull for the custom actions happens at the first step of the build, even before our docker login step, and thus rate limiting still prevails.)
Additional context
In this article (search for silver bullet) - they used an ec2 post install script to authenticate to dockerhub after their ec2s start up such that all requests from the runner to dockerhub are authenticated. Is something similar possible here?
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
No repository files, tests, or concrete entry points are named. Start by locating the runner startup/configuration path and comparing it with the existing Docker login step; done means DockerHub pulls for container-based actions are authenticated before workflow steps run.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, github-actions, kubernetes
- Domain
- authentication, ci-cd, devops, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100