2025-11-15 21:31:20 -07:00
2025-02-16 12:35:01 -06:00
2025-06-01 16:13:44 +08:00
2024-06-13 04:05:23 +08:00
2025-06-01 16:13:44 +08:00
2025-11-15 21:31:20 -07:00
2025-06-01 16:13:44 +08:00

cloudflare-docker-proxy

We are currently observing frequent 429 Too Many Requests errors when this proxy accesses Docker Hub via Cloudflare Worker IP ranges. The root cause is still under investigation, but this issue may lead to unstable pulls or unexpected failures.

Due to the current instability, this project is not recommended for production use. We will provide updates as soon as more information becomes available.

deploy

Deploy to Cloudflare Workers

If you're looking for proxy for helm, maybe you can try cloudflare-helm-proxy.

Deploy

  1. click the "Deploy With Workers" button
  2. follow the instructions to fork and deploy
  3. update routes as you requirement

Deploy to Cloudflare Workers

Routes configuration tutorial

  1. use cloudflare worker host: only support proxy one registry
    const routes = {
      "${workername}.${username}.workers.dev/": "https://registry-1.docker.io",
    };
    
  2. use custom domain: support proxy multiple registries route by host
    • host your domain DNS on cloudflare
    • add A record of xxx.example.com to 192.0.2.1
    • deploy this project to cloudflare workers
    • add xxx.example.com/* to HTTP routes of workers
    • add more records and modify the config as you need
    const routes = {
      "docker.libcuda.so": "https://registry-1.docker.io",
      "quay.libcuda.so": "https://quay.io",
      "gcr.libcuda.so": "https://k8s.gcr.io",
      "k8s-gcr.libcuda.so": "https://k8s.gcr.io",
      "ghcr.libcuda.so": "https://ghcr.io",
    };
    
Description
A docker registry proxy run on cloudflare worker.
Readme 547 KiB
Languages
JavaScript 100%