Fix container CI build workflow #30

New issue

Closed

opened 2026-03-01 22:30:27 +00:00 by mik-tf · 0 comments

mik-tf commented

2026-03-01 22:30:27 +00:00

Member

Context

The build-container.yml workflow fails on every run (#63, #68, #69, #73, #74). The workflow tries to manually start a Docker daemon inside docker:24-dind, but the Forgejo runner with the docker label already provides one. The working hero_services container build (same runner) does not start its own daemon.

Goals

Remove manual dockerd startup step (runner already provides Docker)
Remove fuse-overlayfs from dependencies (not needed)
Use actions/checkout@v4 instead of manual git clone
Align workflow with the proven hero_services/build-container.yaml pattern
Verify container build passes in CI

## Context The `build-container.yml` workflow fails on every run (#63, #68, #69, #73, #74). The workflow tries to manually start a Docker daemon inside `docker:24-dind`, but the Forgejo runner with the `docker` label already provides one. The working `hero_services` container build (same runner) does not start its own daemon. ## Goals - Remove manual `dockerd` startup step (runner already provides Docker) - Remove `fuse-overlayfs` from dependencies (not needed) - Use `actions/checkout@v4` instead of manual `git clone` - Align workflow with the proven `hero_services/build-container.yaml` pattern - Verify container build passes in CI