Publish with a builder on the host's network #6

Merged

jcoffey-dev merged 1 commits from ci/buildx-host-network into main

2026-09-21 23:33:32 +00:00

jcoffey-dev commented

2026-09-21 23:31:04 +00:00

Owner

The first release's image never reached the registry. Both platforms
built, then the push failed:

failed to fetch oauth token: Post "https://git.coffeylabs.org/jwt/auth":
dial tcp 172.30.0.2:443: connect: connection refused

buildx's docker-container builder is a container of its own on the host's
daemon, and it does the push, token and all. On the network it was
created on, git.coffeylabs.org resolves to an internal address with
nothing listening on 443. The job's own docker login worked because it
goes through the host daemon, which resolves the name publicly.
ihasmail's publish failed the same way this morning (job 513), so this is
the runners, not this pipeline.

The builder now runs on the host's network, so it resolves the name as
the login does. Only the token request goes to git.coffeylabs.org; image
layers still go to registry.coffeylabs.org, the registry's DNS-only name.
It gets a new name, ci-builder-host: ci-builder is a long-lived
container shared between jobs, and create || use would keep reusing it
on its old network.

The first release's image never reached the registry. Both platforms built, then the push failed: failed to fetch oauth token: Post "https://git.coffeylabs.org/jwt/auth": dial tcp 172.30.0.2:443: connect: connection refused buildx's docker-container builder is a container of its own on the host's daemon, and it does the push, token and all. On the network it was created on, git.coffeylabs.org resolves to an internal address with nothing listening on 443. The job's own `docker login` worked because it goes through the host daemon, which resolves the name publicly. ihasmail's publish failed the same way this morning (job 513), so this is the runners, not this pipeline. The builder now runs on the host's network, so it resolves the name as the login does. Only the token request goes to git.coffeylabs.org; image layers still go to registry.coffeylabs.org, the registry's DNS-only name. It gets a new name, ci-builder-host: `ci-builder` is a long-lived container shared between jobs, and `create || use` would keep reusing it on its old network.

jcoffey-dev commented

2026-09-21 23:31:04 +00:00

Author

Owner

assigned to @jcoffey-dev