docker-registry-mirror/registry-mirror configuration in arc 0.9.1 #131896
Replies: 1 comment
-
🕒 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.
-
Select Topic Area
Question
Body
I deployed gh actions arc version 0.9.1 and runners are up and scaling.
But when image doesn't exists in artifactory, getting below error:
Error response from daemon: Get "https://registry-1.docker.io/v2/": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
where and how to configure "docker-registry-mirror/registry-mirror" ?? is it in controller values.yaml or in runners values.yaml??
i tried --set "dockerRegistryMirror=artifactory.xyx.com/dockerproxy" in helm install, still no use.
Please advise.
Beta Was this translation helpful? Give feedback.
All reactions