my understanding is that it will help in unstable/disconncted usages

where can I find the schema for config file ? I think I am getting some thing wrong here

I was assuming the first pull will cache the image in local registry

I am trying something like I created two registries

k3d registry create docker-io-proxy \
    --port 0.0.0.0:5100 \
    --proxy-remote-url <https://registry-1.docker.io> \
    --proxy-username "$DOCKERHUB_USERNAME" \
    --proxy-password "$DOCKERHUB_PASSWORD" \
    --volume "<my-vol>:/var/lib/registry"
k3d registry create quay-io-proxy \
    --port 0.0.0.0:5200 \
    --proxy-remote-url <https://quay.io> \
    --proxy-username "$QUAYIO_USERNAME" \
    --proxy-password "$QUAYIO_PASSWORD" \
    --volume "<my-vol>:/var/lib/registry"

apiVersion: <http://k3d.io/v1alpha4|k3d.io/v1alpha4>
kind: Simple
metadata:
  name: dag
servers: 1
# agents: 2
image: rancher/k3s:v1.24.3-k3s1
ports:
  # Drone CI
  - port: 127.0.0.1:30980:30980
    nodeFilters:
      - loadbalancer
  # Gitea
  - port: 127.0.0.1:30950:30950
    nodeFilters:
      - loadbalancer
  # Argo CD
  - port: 127.0.0.1:30080:30080
    nodeFilters:
     - loadbalancer
registries:
  create:
      name: "k3d-myregistry.localhost"
      host: "0.0.0.0"
      hostPort: "5001"
      volumes:
        - "/Users/kameshs/MyLabs/.k3s/registry:/var/lib/registry"
  config: |
      mirrors:
        "<http://docker.io|docker.io>":
           endpoint:
             - "<http://k3d-docker-io-proxy:5100>"
        "<http://quay.io|quay.io>":
           endpoint:
             - "<http://k3d-quay-io-proxy:5200>"

@wide-garage-9465 I tried to compile this discussion on to GH https://github.com/k3d-io/k3d/discussions/1125, can you please share your thoughts when you are at it. Thank you.