Your laptop's Postgres, on the container's loopback

The code runs in your container. The Postgres it needs runs on your laptop: the one loaded with the test fixtures you've curated for a year.

A hoody-tunnel PULL binding puts your laptop's 5432 on the container's loopback: code in the container connects to 127.0.0.1:5432 and lands on the laptop, over the same outbound WebSocket the tunnel already holds. Raw TCP, uninspected: Postgres, Redis, gRPC, anything. Your laptop stays a client in both directions and never opens a listening port.

Reaching backward like this normally means joining both machines to a mesh or standing up a VPN. Here it's one binding, on a session that can hold several.

The database never left the laptop; the loopback just got longer.