Avoid Docker Hub rate limits by pulling through a Vultr Container Registry endpoint such as sjc.vultrcr.com/docker.io.
To help users avoid Docker Hub's rate limits on unauthenticated container image pulls, Vultr provides a public proxy cache through Vultr Container Registry (VCR). This allows users to pull Docker Hub container images via VCR without facing rate restrictions. By leveraging VCR, you can ensure consistent access to container images without unexpected failures due to rate limits.
All public container images on Docker Hub can be accessed through VCR by prefixing the image URL with the appropriate VCR regional endpoint. This method provides a seamless experience for containerized applications, ensuring availability and reducing pull failures caused by Docker Hub restrictions.
Access a container image hosted on Docker Hub via VCR.
Below are some examples for pulling Docker Hub container images through VCR.
Container Image: alpine
Docker Hub
VCR Docker Hub Proxy
Container Image: tensorflow/tensorflow
Docker Hub
VCR Docker Hub Proxy
Container Image: pytorch/pytorch:2.6.0-cuda12.4-cudnn9-runtime
Docker Hub
VCR Docker Hub Proxy
The above examples use sjc.vultrcr.com as the prefix to proxy the requests through the Silicon Valley region.
Use the regional VCR URL closest to your deployment to optimize network performance and ensure reliable access to container images. This helps reduce delays and potential throttling when pulling images from remote locations.
Additionally, using a geographically closer registry can significantly reduce network congestion and improve deployment speed, making it ideal for high-performance workloads and large-scale containerized applications.
Available VCR Regional Endpoints:
ewr.vultrcr.comsgp.vultrcr.comsjc.vultrcr.comams.vultrcr.comblr.vultrcr.comord.vultrcr.comfra.vultrcr.comlax.vultrcr.comlhr.vultrcr.comnrt.vultrcr.comsyd.vultrcr.comsea.vultrcr.com
0 Comments
Be the first to comment and share your perspective with the community.