mirror of
https://github.com/docker/compose.git
synced 2026-11-18 14:13:49 +00:00
The relay container and the relay link networks that stand in for a provider service need three things from the engine: the Docker API, the event bus and whether Docker Desktop is the engine. They now live in internal/relay behind a Backend interface that composeService implements in pkg/compose/relay.go, which keeps the names the lifecycle code calls (ensureServiceRelay, isRelayContainer, checkRelayTarget...) as one-line forwarders, so none of its callers change. The one down-specific piece, turning the relay link networks into down operations gated on the shared limiter, stays in pkg/compose together with its tests; the other relay tests move with the code, assertions unchanged. The progress events and the container name the package needs come from two small shared packages, internal/progress and internal/naming, which the following moves reuse. pkg/compose keeps its own copies until the shared kernel is extracted. Signed-off-by: Nicolas De Loof <nicolas.deloof@gmail.com> |
||
|---|---|---|
| .. | ||
| relay.go | ||
| relay_test.go | ||