Fix container CI: use Docker-in-Docker + buildx + auto-release #26

Merged

mik-tf merged 2 commits from development_fix_container_ci into development

2026-02-28 03:31:00 +00:00

mik-tf commented

2026-02-28 03:29:21 +00:00

Member

Summary

Switch from ubuntu-latest to docker:24-dind (Forgejo runner has no Docker otherwise)
Manual dockerd startup with fuse-overlayfs storage driver
docker/build-push-action@v5 with registry-based buildx caching
docker/login-action@v3 for proper auth
Auto-creates Forgejo release on tag push with pull/run instructions
Tag → :version + :dev, manual dispatch → :version only

Matches the proven hero_services pattern (lhumina_code/hero_services#43).

Closes #25

## Summary - Switch from `ubuntu-latest` to `docker:24-dind` (Forgejo runner has no Docker otherwise) - Manual `dockerd` startup with fuse-overlayfs storage driver - `docker/build-push-action@v5` with registry-based buildx caching - `docker/login-action@v3` for proper auth - Auto-creates Forgejo release on tag push with pull/run instructions - Tag → `:version` + `:dev`, manual dispatch → `:version` only Matches the proven `hero_services` pattern (lhumina_code/hero_services#43). Closes #25

mik-tf added 1 commit

2026-02-28 03:29:21 +00:00

fix: use Docker-in-Docker for container CI workflow

Test / check (pull_request) Has been cancelled

Details

10049b3008

The Forgejo runner doesn't have Docker on ubuntu-latest. Switch to
docker:24-dind with manual dockerd startup, buildx caching, and
auto-release creation — matching the hero_services pattern.

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

mik-tf added 1 commit

2026-02-28 03:30:55 +00:00

fix: increase DinD daemon timeout to 60s

Test / check (pull_request) Successful in 3m9s

Details

aa2d4388e5

30s is too tight for Docker-in-Docker — the nested daemon needs to
initialize fuse-overlayfs storage and networking. 60s is the standard
timeout used by GitHub Actions, GitLab CI, and hero_services.

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