molecule-ai/molecule-core
53
0
Fork 2
Code Issues 184 Pull Requests 40 Actions 3 Packages Projects Releases Wiki Activity

[bug] docker-compose.yml + docker-compose.infra.yml duplicate-service definitions break docker compose build on main #377

New Issue
Closed
opened 2026-05-11 03:54:41 +00:00 by hongming-pc2 · 0 comments
hongming-pc2 commented 2026-05-11 03:54:41 +00:00
Owner
Copy Link
Copy Source

Bug — docker compose build fails with services.langfuse-db-init conflicts with imported resource

Symptom (on main HEAD 108b9a54):

$ cd ~/molecule-core && docker compose build platform
services.langfuse-db-init conflicts with imported resource

Root cause: commit 8cd52fc6 ("infra(docker-compose): include infra services so docker compose up starts Temporal") added a top-level include: - docker-compose.infra.yml to docker-compose.yml, but did NOT remove the now-duplicate service definitions from docker-compose.yml. Both files define the same names:

overlap (services + volumes):
  postgres
  redis
  langfuse-db-init
  pgdata
  redisdata
  clickhousedata

Docker Compose v2 errors out on duplicate definitions between an include: and the main file — so right now docker compose build/up on main is broken for everyone who doesn't have a pre-built molecule-core-platform:latest image in their local Docker cache.

Impact: any first-clone or post-docker system prune developer can't bring up the local stack. Discovered while trying to redeploy the platform image to pick up the PR #331 (issue #310) ResponseHeaderTimeout 60→180s fix — workaround was direct docker build -f workspace-server/Dockerfile ., but that's not the documented developer flow.

Suggested fix (one of):

  1. Remove duplicates from docker-compose.yml — let include: docker-compose.infra.yml be the SSOT for postgres/redis/langfuse-db-init/volumes. Simpler. Matches the intent of 8cd52fc6. Easy follow-up to 40736a41 (digest pinning).
  2. Drop the include: directive — revert the intent of 8cd52fc6 and require users to docker compose -f docker-compose.yml -f docker-compose.infra.yml up explicitly. More work for users.

Option 1 is the cleaner fix. Should also update 40736a41's digest pins so they live in docker-compose.infra.yml (one place), not both.

Severity: medium (blocks local-stack bootstrap; existing deployments unaffected; workaround = direct docker build).

Reproduction:

$ git checkout main && git pull
$ docker compose build platform
services.langfuse-db-init conflicts with imported resource

Workaround:

$ docker build -f workspace-server/Dockerfile -t molecule-core-platform:latest .
$ docker compose up -d --no-build platform

Filed by hongming-pc2 while restarting platform to pick up #310's ResponseHeaderTimeout fix.

## Bug — `docker compose build` fails with `services.langfuse-db-init conflicts with imported resource` **Symptom (on `main` HEAD `108b9a54`):** ``` $ cd ~/molecule-core && docker compose build platform services.langfuse-db-init conflicts with imported resource ``` **Root cause:** commit `8cd52fc6` ("infra(docker-compose): include infra services so `docker compose up` starts Temporal") added a top-level `include: - docker-compose.infra.yml` to `docker-compose.yml`, but did NOT remove the now-duplicate service definitions from `docker-compose.yml`. Both files define the same names: ``` overlap (services + volumes): postgres redis langfuse-db-init pgdata redisdata clickhousedata ``` Docker Compose v2 errors out on duplicate definitions between an `include:` and the main file — so right now `docker compose build/up` on main is **broken** for everyone who doesn't have a pre-built `molecule-core-platform:latest` image in their local Docker cache. **Impact:** any first-clone or post-`docker system prune` developer can't bring up the local stack. Discovered while trying to redeploy the platform image to pick up the PR #331 (issue #310) `ResponseHeaderTimeout 60→180s` fix — workaround was direct `docker build -f workspace-server/Dockerfile .`, but that's not the documented developer flow. **Suggested fix (one of):** 1. **Remove duplicates from `docker-compose.yml`** — let `include: docker-compose.infra.yml` be the SSOT for postgres/redis/langfuse-db-init/volumes. Simpler. Matches the intent of `8cd52fc6`. Easy follow-up to `40736a41` (digest pinning). 2. **Drop the `include:` directive** — revert the intent of `8cd52fc6` and require users to `docker compose -f docker-compose.yml -f docker-compose.infra.yml up` explicitly. More work for users. Option 1 is the cleaner fix. Should also update `40736a41`'s digest pins so they live in `docker-compose.infra.yml` (one place), not both. **Severity:** medium (blocks local-stack bootstrap; existing deployments unaffected; workaround = direct `docker build`). **Reproduction:** ``` $ git checkout main && git pull $ docker compose build platform services.langfuse-db-init conflicts with imported resource ``` Workaround: ``` $ docker build -f workspace-server/Dockerfile -t molecule-core-platform:latest . $ docker compose up -d --no-build platform ``` Filed by hongming-pc2 while restarting platform to pick up #310's ResponseHeaderTimeout fix.
triage-operator added the tier:low label 2026-05-11 04:23:10 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area/ci
CI/CD pipeline issues
 do-not-auto-merge
Opt out of autonomous merge-queue merging
 do-not-merge
hold from auto-merge (design review in progress)
 kind/infrastructure
Infrastructure-related issues
 merge-queue
Ready for serialized Gitea merge queue
 merge-queue-hold
Temporarily hold PR in merge queue
 platform/go
Go platform test issues
 release-blocker
Blocks the staging→main promotion / a release
 release-test
security
test-label-sre
tier:high
High risk per dev-sop §SOP-6 — ceo only, 24h cooldown
 tier:low
Low risk per dev-sop §SOP-6 — engineers/managers/ceo can approve
 tier:medium
Medium risk per dev-sop §SOP-6 — managers/ceo can approve
 triage-test
test
 wip
Work in progress — do not auto-merge
No Label tier:low
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
agent-dev-a agent-dev-b agent-pm agent-researcher agent-reviewer agent-reviewer-1 agent-reviewer-cr2 app-fe (Molecule AI · app-fe) app-lead (Molecule AI · app-lead) app-qa (Molecule AI · app-qa) claude-ceo-assistant claude-ci-reader claude-status-reaper core-be (Molecule AI · core-be) core-devops (Molecule AI · core-devops) core-fe (Molecule AI · core-fe) core-lead (Molecule AI · core-lead) core-offsec (Molecule AI · core-offsec) core-qa (Molecule AI · core-qa) core-security (Molecule AI · core-security) core-uiux (Molecule AI · core-uiux) cp-be (Molecule AI · cp-be) cp-lead (Molecule AI · cp-lead) cp-qa (Molecule AI · cp-qa) cp-security (Molecule AI · cp-security) cui (Zhanlin Cui) dev-lead (Molecule AI · dev-lead) devops-engineer documentation-specialist (Molecule AI · documentation-specialist) fullstack-engineer (Molecule AI · fullstack-engineer) godwin hongming hongming-ceo-delegated hongming-codex-laptop hongming-kimi-laptop hongming-pc2 hongming-personal infra-lead (Molecule AI · infra-lead) infra-runtime-be (Molecule AI · infra-runtime-be) infra-sre (Molecule AI · infra-sre) integration-tester (Molecule AI · integration-tester) mc-drift-bot molecule-code-reviewer plugin-dev (Molecule AI · plugin-dev) pm publish-runtime-bot pypi-publisher (Molecule AI PyPI Publisher (RFC#596)) release-manager (Molecule AI · release-manager) sdk-dev (Molecule AI · sdk-dev) sdk-lead (Molecule AI · sdk-lead) sop-drift-bot sop-tier-bot (SOP Tier-Check Bot) technical-writer (Molecule AI · technical-writer) triage-operator (Molecule AI · triage-operator)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: molecule-ai/molecule-core#377
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?