In this article:
Applicable to
- Twingate Component: Connector
- 3rd Party: Azure Cloud Services
Overview
Some users deploying, or updating, Twingate Connectors using the Azure Container Services, are encountering the error:
(RegistryErrorResponse) An error response is received from the docker registry 'index.docker.io'. Please retry later.
Code: RegistryErrorResponse
When updating connectors you may see an error along the lines of:
Failed to restart the container group '<container group name>'. Error: An error response is received from the docker registry 'index.docker.io'. Please retry later.
Cause
Docker Hub rate-limiting is the primary cause for this error.
Resolution
Authenticate requests with Docker Hub credentials
Docker Hub's rate limiting provides higher rate-limiting thresholds for authenticated and paid users, as outlined in their rate-limiting documentation page.
When deploying Twingate Connectors using Azure Container Instances, you can authenticate your Twingate Connector image pull requests by adding the following parameters to the deployment command:
--registry-username [dockerhub username] --registry-password [dockerhub password] --registry-login-server index.docker.io
For further reading, please reference the Azure az container command's reference page.