eblume/blumeops
1
1
Fork 0
Code Issues Pull requests Projects Releases 83 Packages Wiki Activity Actions
blumeops/argocd/manifests/forgejo-runner
History
Erich Blume d5c00192d5 Configure DinD to use Zot as pull-through registry mirror (#183) 
## 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

Reviewed-on: https://forge.ops.eblu.me/eblume/blumeops/pulls/183
2026-02-13 12:36:03 -08:00
..
configmap.yaml Configure DinD to use Zot as pull-through registry mirror (#183) 2026-02-13 12:36:03 -08:00
deployment.yaml Configure DinD to use Zot as pull-through registry mirror (#183) 2026-02-13 12:36:03 -08:00
external-secret.yaml Move non-secret runner env vars to deployment spec (#181) 2026-02-13 10:29:23 -08:00
namespace.yaml Migrate Forgejo runner to Kubernetes with DinD (#60) 2026-01-25 19:56:17 -08:00