compose/pkg/api
Nicolas De Loof 27c9a231ea feat(compose): dedicated network for the provider relay link
get-relay-info answers pointed a locally-bound provider at one of the
dependents' own networks: shared infrastructure every other service on
it could also reach, and no more isolated than any project bridge.

Provision a dedicated, internal:true bridge network scoped to that one
provider service instead, created only when the provider itself sends
get-relay-info -- the provider's own declaration that it binds locally,
never for a provider backing a remote resource. The relay container
joins it alongside the dependents' networks it already joins; it is
torn down with the relay on endpoint changes and on down, including
the no-compose-file down path.

The network's lifecycle is hardened against the races a shared,
project-scoped resource runs into:

- a NetworkCreate conflict on the deterministic name re-checks by
  label (not just by name) before adopting the existing network, so a
  genuine name clash with an unrelated, user-declared network fails
  loudly instead of being silently adopted into the relay's isolation
  boundary;
- a NotFound gateway lookup after losing that conflict falls back to
  an unresolved answer instead of propagating the error;
- removeRelayLinkNetwork and ensureRelayLinkNetworksDown both tolerate
  a NetworkRemove conflict from the daemon's asynchronous endpoint
  disconnect, which can race the relay container's own removal;
- ensureRelayLinkNetworksDown accumulates failures with errors.Join
  across every relay-link network of a project instead of aborting on
  the first one, and skips (warn-only) a network that still has active
  endpoints, mirroring removeNetwork's existing tolerance for regular
  project networks.

docs/extension.md documents that the "desktop" network name in the
get-relay-info answer (under Docker Desktop) is an opaque placeholder,
never a real Docker network a provider can inspect or connect to.

Signed-off-by: Nicolas De Loof <nicolas.deloof@gmail.com>
2026-10-02 12:33:26 +02:00
..
api.go fix(port): preserve tie order for dual-stack port publishers 2026-09-14 10:48:03 +02:00
api_test.go build(deps): adopt compose-go jobs and the container-spec layering 2026-09-21 16:35:20 +02:00
context.go Introduce abstractions to support SDK usage without requiring Docker CLI 2025-10-27 16:17:50 +01:00
env.go restore support for COMPOSE_COMPATIBILITY 2025-12-07 18:42:04 +01:00
errors.go move progress UI components into cmd 2025-11-12 11:17:28 +01:00
errors_test.go deps: remove deprecated github.com/pkg/errors 2023-09-29 06:28:58 +02:00
event.go add 'configured' event at the end of model configuration phase 2025-12-15 10:14:21 +01:00
labels.go feat(compose): dedicated network for the provider relay link 2026-10-02 12:33:26 +02:00
labels_test.go golangci-lint: use gci formatter instead of goimports 2025-12-01 12:21:50 +01:00