Configure DinD to use Zot as pull-through registry mirror #183

Merged

eblume merged 1 commit from feature/dind-zot-registry-mirror into main

2026-02-13 12:36:04 -08:00

eblume commented

2026-02-13 12:35:23 -08:00

Owner

Summary

Add daemon.json with registry-mirrors to the forgejo-runner ConfigMap, pointing DinD at http://host.minikube.internal:5050
Mount daemon.json into the DinD sidecar at /etc/docker/daemon.json via subPath
Docker Hub pulls during Dagger CI builds will now route through Zot's pull-through cache, reducing bandwidth and avoiding rate limits

Deployment and Testing

argocd app sync forgejo-runner
Exec into DinD container: docker info should show the registry mirror
Trigger a workflow build and check Zot logs for cache hits

## Summary - Add `daemon.json` with `registry-mirrors` to the forgejo-runner ConfigMap, pointing DinD at `http://host.minikube.internal:5050` - Mount `daemon.json` into the DinD sidecar at `/etc/docker/daemon.json` via `subPath` - Docker Hub pulls during Dagger CI builds will now route through Zot's pull-through cache, reducing bandwidth and avoiding rate limits ## Deployment and Testing - [ ] `argocd app sync forgejo-runner` - [ ] Exec into DinD container: `docker info` should show the registry mirror - [ ] Trigger a workflow build and check Zot logs for cache hits

eblume added 1 commit

2026-02-13 12:35:24 -08:00

Configure DinD sidecar to use Zot as pull-through registry mirror 43d510cd50

Route Docker Hub pulls from the forgejo-runner DinD sidecar through
the existing Zot cache at host.minikube.internal:5050, reducing
bandwidth usage and avoiding Docker Hub rate limits during CI builds.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>