mirror of
https://github.com/docker/compose.git
synced 2026-11-17 13:45:39 +00:00
A provider running its service LOCALLY has to pick the address its published endpoint binds, and on a standalone Linux engine no address is both relay-reachable and off the LAN (#14257): host.docker.internal resolves there to the bridge gateway, which a loopback-only listener cannot accept, while the wildcard exposes the port on every host interface. The bundled example provider worked around it by binding 0.0.0.0. The new get-relay-info message closes that gap, with compose owning the platform knowledge so the provider just binds what is announced. Compose answers with one JSON line listing the networks the relay would join — the dependents' networks, exactly as selected for the relay deployment — each with the address a locally-run endpoint should bind to be reachable from the relay: the network's engine-assigned gateway on a standalone engine (an address the host owns on that bridge, reachable from the relay but not from the LAN), and 127.0.0.1 under Docker Desktop — the networks live inside the VM there, and the host's own loopback is, factually, where a host process is reached through the Desktop proxy. Resolution is lazy (Desktop detection and network inspects run only when a provider asks — a remote-resource provider never does) and best-effort: a missing gateway means "bind elsewhere". Compose also announces the message types it accepts in the COMPOSE_PROVIDER_MESSAGES environment variable of the provider process: an unknown message stays a fatal protocol error by design (a provider REQUIRING an unsupported message must fail loudly), and the announcement is how a provider adapts instead of failing. The example provider binds the first announced gateway, falling back to the wildcard only when none is announced; through it, TestProviderPublishEndpoint exercises the gateway path on Linux CI and the loopback path on Docker Desktop. Signed-off-by: Nicolas De Loof <nicolas.deloof@gmail.com> |
||
|---|---|---|
| .. | ||
| examples | ||
| reference | ||
| yaml/main | ||
| extension.md | ||
| sdk.md | ||