CLP package startup fails with Docker Compose v5.3.x when telemetry is disabled

[junhaoliao]

Bug

When starting a CLP package with telemetry disabled, ./sbin/start-clp.sh can fail even after the expected CLP services have been created or started. The startup command runs Docker Compose with up --detach --wait; with telemetry disabled, the generated package environment disables otel-collector, but Docker Compose v5.3.1 still exits with:

clp-package-eda5cf1e-b09a-4be4-9789-49d59cf55e3c is missing dependency otel-collector

Expected behavior: CLP should start successfully with telemetry disabled, and disabling telemetry should not make startup wait for or require otel-collector.

This appears related to the Docker Compose v5.3.x zero-replica dependency regression tracked upstream in docker/compose#13899.

CLP version

6ed4fffcdf2eb5cb93b85417f488a9cad2005f31

Environment

• OS: Ubuntu 22.04.5 LTS
• Docker Compose: Docker Compose version v5.3.1
• Docker Engine: Client 29.6.1, Server 29.6.1
• Package path: build/clp-package
• Generated package environment:
  • CLP_DISABLE_TELEMETRY=true
  • CLP_OTEL_COLLECTOR_ENABLED=0

Reproduction steps

1. Build or otherwise prepare a CLP package at build/clp-package.

2. Ensure telemetry is disabled in the package environment, for example:

   CLP_DISABLE_TELEMETRY=true
   CLP_OTEL_COLLECTOR_ENABLED=0
   

3. Start the package:

   cd build/clp-package
   ./sbin/start-clp.sh

4. Observe that startup reaches the Docker Compose wait step, creates/starts the expected CLP services, then exits non-zero with:

   clp-package-eda5cf1e-b09a-4be4-9789-49d59cf55e3c is missing dependency otel-collector
   

[junhaoliao]

opened PR docker/compose#13931 to fix it in the upstream