karti e6b4c1618e CI: reach Postgres through the gateway instead of a shared namespace ...

Second attempt failed differently: /etc/hostname inside the job reports the
HOST's name rather than the container id, so `--network container:$HOSTNAME`
found no such container.

Rather than hunt for our own container id through /proc, publish the port on
the host and connect through the job container's default gateway. That needs
no container identity at all. The port is derived from the run id so two
concurrent runs cannot collide, and DATABASE_URL is exported through GITHUB_ENV
once Postgres is actually accepting connections.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

2026-08-12 20:30:24 -07:00

..

workflows

CI: reach Postgres through the gateway instead of a shared namespace

2026-08-12 20:30:24 -07:00