langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-20 19:50:06 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

Docker compose up fails on mac #22142

New Issue
Open
opened 2026-02-21 20:15:56 -05:00 by yindo · 5 comments
yindo commented 2026-02-21 20:15:56 -05:00
Owner
Copy Link
Copy Source

Originally created by @snimavat on GitHub (Feb 8, 2026).

Self Checks

  • I have read the Contributing Guide and Language Policy.
  • This is only for bug report, if you would like to ask a question, please head to Discussions.
  • I have searched for existing issues search for existing issues, including closed ones.
  • I confirm that I am using English to submit this report, otherwise it will be closed.
  • 【中文用户 & Non English User】请使用英语提交，否则会被关闭 ：）
  • Please do not modify this template :) and fill in all the required fields.

Dify version

1.12.1

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Just checked out branch 1.12.1
cd into ./docker dir
cp .env.example .env
docker compose up

Fails with error

docker compose up
validating /Users/xxxx/dify/docker/docker-compose.yaml: services.plugin_daemon.depends_on.db_mysql Additional property required is not allowed

Docker Compose version v2.19.1
OS : Mac 12.7.4

✔️ Expected Behavior

Docker compose up should work out of the box on fresh checkout

❌ Actual Behavior

Docker compose up fails on validating the schema

Originally created by @snimavat on GitHub (Feb 8, 2026). ### Self Checks - [x] I have read the [Contributing Guide](https://github.com/langgenius/dify/blob/main/CONTRIBUTING.md) and [Language Policy](https://github.com/langgenius/dify/issues/1542). - [x] This is only for bug report, if you would like to ask a question, please head to [Discussions](https://github.com/langgenius/dify/discussions/categories/general). - [x] I have searched for existing issues [search for existing issues](https://github.com/langgenius/dify/issues), including closed ones. - [x] I confirm that I am using English to submit this report, otherwise it will be closed. - [x] 【中文用户 & Non English User】请使用英语提交，否则会被关闭 ：） - [x] Please do not modify this template :) and fill in all the required fields. ### Dify version 1.12.1 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce Just checked out branch 1.12.1 cd into ./docker dir cp .env.example .env docker compose up Fails with error ``` docker compose up validating /Users/xxxx/dify/docker/docker-compose.yaml: services.plugin_daemon.depends_on.db_mysql Additional property required is not allowed ``` Docker Compose version v2.19.1 OS : Mac 12.7.4 ### ✔️ Expected Behavior Docker compose up should work out of the box on fresh checkout ### ❌ Actual Behavior Docker compose up fails on validating the schema
yindo added the 🐞 bug🙏 help wanted labels 2026-02-21 20:15:56 -05:00
yindo commented 2026-02-21 20:15:56 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Feb 8, 2026):

Hi @snimavat! I'm Dosu and I’m helping the dify team.

This error happens because the depends_on section in the compose file uses nested properties (condition and required) that aren't supported by Docker Compose v2.19.1. Newer versions (29.1.2 or higher) support this syntax and will resolve the validation error—so upgrading Docker Compose is the recommended fix source.

If upgrading isn't possible, you can manually edit the compose file: replace the nested depends_on blocks with a simple list of service names (for example, depends_on: [db_mysql, db_postgres, redis]). This workaround removes the unsupported properties, but you lose the health/condition checks.

Let me know if you need a sample edit or run into any other issues.

To reply, just mention @dosu.

How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other

Chat with Dosu Open in Cursor Join Discord Share on X

@dosubot[bot] commented on GitHub (Feb 8, 2026): <!-- Greeting --> Hi @snimavat! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the dify team. <!-- Answer --> This error happens because the `depends_on` section in the compose file uses nested properties (`condition` and `required`) that aren't supported by Docker Compose v2.19.1. Newer versions (29.1.2 or higher) support this syntax and will resolve the validation error—so upgrading Docker Compose is the recommended fix [source](https://github.com/langgenius/dify/issues/28587). If upgrading isn't possible, you can manually edit the compose file: replace the nested `depends_on` blocks with a simple list of service names (for example, `depends_on: [db_mysql, db_postgres, redis]`). This workaround removes the unsupported properties, but you lose the health/condition checks. Let me know if you need a sample edit or run into any other issues. <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/13e65558-9128-43d9-9b63-ee69866cf1fc?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/13e65558-9128-43d9-9b63-ee69866cf1fc?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/13e65558-9128-43d9-9b63-ee69866cf1fc?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/13e65558-9128-43d9-9b63-ee69866cf1fc?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/13e65558-9128-43d9-9b63-ee69866cf1fc?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/13e65558-9128-43d9-9b63-ee69866cf1fc?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/13e65558-9128-43d9-9b63-ee69866cf1fc?feedback_type=other)</sup> [![Chat with Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/6088a4f4-073a-43f3-b3d4-4f06fb0c05a0/ask?utm_source=github)&nbsp;[![Open in Cursor](https://dosu.dev/dosu-in-cursor.svg)](https://cursor.com/link/prompt?text=This%20error%20happens%20because%20the%20%60depends_on%60%20section%20in%20the%20compose%20file%20uses%20nested%20properties%20%28%60condition%60%20and%20%60required%60%29%20that%20aren%27t%20supported%20by%20Docker%20Compose%20v2.19.1.%20Newer%20versions%20%2829.1.2%20or%20higher%29%20support%20this%20syntax%20and%20will%20resolve%20the%20validation%20error%E2%80%94so%20upgrading%20Docker%20Compose%20is%20the%20recommended%20fix%20%5Bsource%5D%28https%3A//github.com/langgenius/dify/issues/28587%29.%0A%0AIf%20upgrading%20isn%27t%20possible%2C%20you%20can%20manually%20edit%20the%20compose%20file%3A%20replace%20the%20nested%20%60depends_on%60%20blocks%20with%20a%20simple%20list%20of%20service%20names%20%28for%20example%2C%20%60depends_on%3A%20%5Bdb_mysql%2C%20db_postgres%2C%20redis%5D%60%29.%20This%20workaround%20removes%20the%20unsupported%20properties%2C%20but%20you%20lose%20the%20health/condition%20checks.%0A%0ALet%20me%20know%20if%20you%20need%20a%20sample%20edit%20or%20run%20into%20any%20other%20issues.)&nbsp;[![Join Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot)&nbsp;[![Share on X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/langgenius/dify/issues/32110)
yindo commented 2026-02-21 20:15:56 -05:00
Author
Owner
Copy Link
Copy Source

@snimavat commented on GitHub (Feb 9, 2026):

Would be great if it can support 24x versions of docker, and atleast update docs for this gotchas

Blocker for users who are on mac 12.x :

Users who are on mac 12.x can not use newer versions of docker, and hence can not run the dify otherwise without manually changing the compose file

@snimavat commented on GitHub (Feb 9, 2026): Would be great if it can support 24x versions of docker, and atleast update docs for this gotchas **Blocker** for users who are on mac 12.x : **Users who are on mac 12.x can not use newer versions of docker**, and hence can not run the dify otherwise without manually changing the compose file
yindo commented 2026-02-21 20:15:56 -05:00
Author
Owner
Copy Link
Copy Source

@fatelei commented on GitHub (Feb 9, 2026):

you can remove all required

sed -i '/required: false/d' docker-compose.yaml
sed -i '/required: true/d' docker-compose.yaml
@fatelei commented on GitHub (Feb 9, 2026): you can remove all required ``` sed -i '/required: false/d' docker-compose.yaml sed -i '/required: true/d' docker-compose.yaml ```
yindo commented 2026-02-21 20:15:56 -05:00
Author
Owner
Copy Link
Copy Source

@snimavat commented on GitHub (Feb 9, 2026):

@fatelei I think it needs more tinkering the removing just required flag.
different containers, eg mysql, pgsql are used based on profile.
After removing required docker will fail with errors such as service db_mysql is required by plugin_daemon but is disabled. Can be enabled by profiles [mysql]

@snimavat commented on GitHub (Feb 9, 2026): @fatelei I think it needs more tinkering the removing just `required` flag. different containers, eg mysql, pgsql are used based on profile. After removing `required` docker will fail with errors such as `service db_mysql is required by plugin_daemon but is disabled. Can be enabled by profiles [mysql]`
yindo commented 2026-02-21 20:15:56 -05:00
Author
Owner
Copy Link
Copy Source

@fatelei commented on GitHub (Feb 9, 2026):

@fatelei I think it needs more tinkering the removing just required flag. different containers, eg mysql, pgsql are used based on profile. After removing required docker will fail with errors such as service db_mysql is required by plugin_daemon but is disabled. Can be enabled by profiles [mysql]

you can also remove profile

@fatelei commented on GitHub (Feb 9, 2026): > [@fatelei](https://github.com/fatelei) I think it needs more tinkering the removing just `required` flag. different containers, eg mysql, pgsql are used based on profile. After removing `required` docker will fail with errors such as `service db_mysql is required by plugin_daemon but is disabled. Can be enabled by profiles [mysql]` you can also remove profile
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Knowledge Pipeline
Proposal
WIP
cloud
dependencies
feat:webapp
good first issue
outdated
performance
pull-request
Mirrored from GitHub Pull Request
 python:uv
refactor
size:L
stale
status: accepting prs
status: blocked
status: in discussion
stt & tts
vulnerablity
web
wont-fix
🌊 feat:workflow
🌚 invalid
🐞 bug
👻 feat:rag
💪 enhancement
📚 documentation
🔨 feat:tools
🙋‍♂️ question
🙏 help wanted
🤔 cant-reproduce
🤖 feat:agent
No Label 🐞 bug 🙏 help wanted
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#22142
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?