From 690ca3ff5ff6ad3e88cfc7c6dcaa6138b9be4c4c Mon Sep 17 00:00:00 2001 From: Nicolas De Loof Date: Tue, 22 Sep 2026 14:36:07 +0200 Subject: [PATCH] fix(start): a project made only of provider services could not start MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit startService errored with 'no container to start' whenever the project-wide container listing came back empty, before the per-service filtering that lets provider services pass through. A project whose services are all provider-backed legitimately reaches the start phase with zero containers. The empty-list error is now softened for provider services only — a relay container deployed for published endpoints still goes through the regular start path. Signed-off-by: Nicolas De Loof --- pkg/compose/service_containers.go | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/pkg/compose/service_containers.go b/pkg/compose/service_containers.go index 2337765ad..0ac19ee9b 100644 --- a/pkg/compose/service_containers.go +++ b/pkg/compose/service_containers.go @@ -591,7 +591,6 @@ func (s *composeService) startService(ctx context.Context, if service.Deploy != nil && service.Deploy.Replicas != nil && *service.Deploy.Replicas == 0 { return nil } - err := s.waitDependencies(ctx, project, service.Name, service.DependsOn, containers, timeout) if err != nil { return err @@ -601,6 +600,13 @@ func (s *composeService) startService(ctx context.Context, if service.GetScale() == 0 { return nil } + if service.Provider != nil { + // a provider-backed service usually has no container of its own + // (it gets one — the relay — only when the provider published + // endpoints), so a project made only of provider services + // legitimately reaches the start phase with no container at all + return nil + } return errNoContainerToStart(service.Name) }