container.options: --add-host=docker-host:host-gateway in the runner's
config is meant to make "docker-host" resolve inside job containers, but
that alias isn't landing on the publish job's container (DNS lookup of
docker-host fails there). act_runner's own connection to the same daemon
does resolve it, via the pod's hostAliases entry to 172.17.0.1 (proven by
verify's Postgres service container working over it). Point DOCKER_HOST
at that address directly instead of depending on the container-option
alias.
This is a stopgap: it hardcodes a node-internal bridge IP into the
workflow. The real fix is on the runner side, figuring out why
container.options isn't reaching job containers.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>