Forgejo CI Docker-in-Docker base image (insecure-registries patch for forgejo:3000)
  • Dockerfile 100%
Find a file
Arlind 6a8b069232
All checks were successful
Build and push custom-dind / Build & push custom-dind (push) Successful in 7s
ci: dind on :2375
2026-05-17 06:05:36 +02:00
.gitea/workflows ci: dind on :2375 2026-05-17 06:05:36 +02:00
daemon.json Initial: custom-dind base + build.yml 2026-05-17 05:48:02 +02:00
Dockerfile Disable docker:dind TLS on :2376 2026-05-17 05:58:53 +02:00
README.md Initial: custom-dind base + build.yml 2026-05-17 05:48:02 +02:00

custom-dind

Forgejo CI Docker-in-Docker base image.

Wraps docker:dind with /etc/docker/daemon.json declaring forgejo:3000 as an insecure registry so the act_runner can docker login + push images via the internal Forgejo container registry on plain HTTP.

Used by the forgejo-dind service in /home/arlind/docker/forgejo/docker-compose.yml.

Operational notes

daemon.json is loaded once at dockerd startup. If you edit it on a running container, send SIGHUP to dockerd:

docker exec forgejo-dind pkill -HUP dockerd

Symptom of missed reload: runner jobs fail with http: server gave HTTP response to HTTPS client on push.