The ci-image.yml build was failing because the DinD build environment could not resolve deb.debian.org, so apt install docker.io failed and python-repositories-ci:latest was never published. That blocked PRs using runs-on: python-repositories-ci.
Copy the Docker CLI from docker:27-cli instead of installing docker.io via apt (only the CLI is needed for testcontainers)
Add --network=host to docker build in the workflow and build-ci-image.sh so builds use the host DNS resolver
Test plan
Merge to main
Run Build CI Image (workflow_dispatch) and confirm it completes successfully
Verify gitea.lille-vemmelund.dk/brian/python-repositories-ci:latest exists in the registry
Re-run the blocked python-repositories-ci PR workflows
If needed, restart homelab-cluster-gitea-runner-0 to clear the DinD RWLayer error
## Summary
The `ci-image.yml` build was failing because the DinD build environment could not resolve `deb.debian.org`, so `apt install docker.io` failed and `python-repositories-ci:latest` was never published. That blocked PRs using `runs-on: python-repositories-ci`.
- Copy the Docker CLI from `docker:27-cli` instead of installing `docker.io` via apt (only the CLI is needed for testcontainers)
- Add `--network=host` to `docker build` in the workflow and `build-ci-image.sh` so builds use the host DNS resolver
## Test plan
- [ ] Merge to `main`
- [ ] Run **Build CI Image** (`workflow_dispatch`) and confirm it completes successfully
- [ ] Verify `gitea.lille-vemmelund.dk/brian/python-repositories-ci:latest` exists in the registry
- [ ] Re-run the blocked `python-repositories-ci` PR workflows
- [ ] If needed, restart `homelab-cluster-gitea-runner-0` to clear the DinD `RWLayer` error
Copy the Docker CLI from the official image instead of apt, and use
--network=host during docker build so apt and layer pulls can resolve
external registries on standalone runners.
Co-authored-by: Cursor <[email protected]>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
The
ci-image.ymlbuild was failing because the DinD build environment could not resolvedeb.debian.org, soapt install docker.iofailed andpython-repositories-ci:latestwas never published. That blocked PRs usingruns-on: python-repositories-ci.docker:27-cliinstead of installingdocker.iovia apt (only the CLI is needed for testcontainers)--network=hosttodocker buildin the workflow andbuild-ci-image.shso builds use the host DNS resolverTest plan
mainworkflow_dispatch) and confirm it completes successfullygitea.lille-vemmelund.dk/brian/python-repositories-ci:latestexists in the registrypython-repositories-ciPR workflowshomelab-cluster-gitea-runner-0to clear the DinDRWLayererrorTest Coverage Report: