ashwin/nxtgauge-backend-rust
0
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

fix(ci): route job-container DOCKER_HOST via host.docker.internal
Some checks failed
build-and-release / build (push) Failing after 16s
Details

Browse source 
127.0.0.1:2375 only worked from the runner container's own network
namespace (sibling to the dind sidecar in the same pod). The actual
job container that runs each step is spawned *by* that dind engine,
one level deeper, so its own loopback doesn't reach the sidecar.
host.docker.internal (mapped to the job container's real gateway via
--add-host=host.docker.internal:host-gateway in the runner's
container.options) reaches back to the dind engine that created it.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This commit is contained in:
Ashwin Kumar Sivakumar 2026-07-07 19:59:27 +05:30
parent e6e503ca69
commit b9e0ba247c
1 changed files with 6 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

7
.forgejo/workflows/build.yaml
View file

@ -14,7 +14,12 @@ jobs:
build:
runs-on: docker-ready
env:
DOCKER_HOST: tcp://127.0.0.1:2375
# 127.0.0.1 doesn't work here: the job container is nested one level
# inside the runner pod's dind sidecar, so its own loopback isn't the
# sidecar's. host.docker.internal (mapped via --add-host in the
# runner's container.options) reaches back to the dind engine that
# actually spawned this container.
DOCKER_HOST: tcp://host.docker.internal:2375
DOCKER_BUILDKIT: "1"
steps:
- name: Checkout