Configure Docker Registry Mirrors on GitHub Hosted Runners #154626
Replies: 2 comments
-
|
🕒 Discussion Activity Reminder 🕒 This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions: 1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as 2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own. 3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution. Note: This dormant notification will only apply to Discussions with the Thank you for helping bring this Discussion to a resolution! 💬 |
Beta Was this translation helpful? Give feedback.
-
|
Quite relevant with the docer.io outage today 😢 |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Select Topic Area
Question
Body
Docker supports Image registry mirrors. With the recent enforcement of a rate limit of 10 pulls/hour for unauthenticated users, mirrors play a critical role in making sure images remain accessible to GitHub Actions workflows that rely on pulling images. Without mirrors, we are consistently running into this rate limit, and our Actions that pull Docker images are failing.
There currently seems to be no mechanism to configure mirrors for GitHub-hosted runners. Attempting to manually overwrite the Docker configuration file at
/etc/docker/daemon.jsonresults in permission denied, even when usingsudo.As one example, actions-runner-controller implemented this by adding a configuration option and environment variable used to configure Docker.
How can I configure Docker Registry Mirrors on GitHub-hosted runners?
Beta Was this translation helpful? Give feedback.
All reactions