langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-21 12:05:30 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

start up error:Additional property required is not allowed #20511

New Issue
Closed
opened 2026-02-21 20:07:46 -05:00 by yindo · 9 comments
yindo commented 2026-02-21 20:07:46 -05:00
Owner
Copy Link
Copy Source

Originally created by @Chenxiuling-Amy on GitHub (Nov 24, 2025).

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.10.0

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

when run the command:
docker compose up -d
i get the error:
docker-compose.yaml: services.plugin_daemon.depends_on.db_postgres Additional property required is not allowed

✔️ Expected Behavior

System started successfully.

❌ Actual Behavior

when run the command:
docker compose up -d
i get the error:
docker-compose.yaml: services.plugin_daemon.depends_on.db_postgres Additional property required is not allowed

Originally created by @Chenxiuling-Amy on GitHub (Nov 24, 2025). ### 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.10.0 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce when run the command: docker compose up -d i get the error: docker-compose.yaml: services.plugin_daemon.depends_on.db_postgres Additional property required is not allowed ### ✔️ Expected Behavior System started successfully. ### ❌ Actual Behavior when run the command: docker compose up -d i get the error: docker-compose.yaml: services.plugin_daemon.depends_on.db_postgres Additional property required is not allowed
yindo added the 🐞 bugstale labels 2026-02-21 20:07:46 -05:00
yindo closed this issue 2026-02-21 20:07:46 -05:00
yindo commented 2026-02-21 20:07:46 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Nov 24, 2025):

The error is caused by the unsupported required property in the depends_on section for the plugin_daemon service in your docker-compose.yaml. Docker Compose does not allow a required field in service dependencies—only condition is supported for healthchecks. To fix this, remove every required: false line under each dependency in plugin_daemon.depends_on so only condition: service_healthy remains. For example:

depends_on:
  db_postgres:
    condition: service_healthy
  db_mysql:
    condition: service_healthy
  oceanbase:
    condition: service_healthy
  seekdb:
    condition: service_healthy

If your compose file is auto-generated, update the template or .env.example and regenerate the file instead of editing it directly. After making these changes, rerun docker compose up -d and the error should be resolved.
Reference: Official docker-compose.yaml for Dify v1.10.0

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 (Nov 24, 2025): <!-- Answer --> The error is caused by the unsupported `required` property in the `depends_on` section for the `plugin_daemon` service in your docker-compose.yaml. Docker Compose does not allow a `required` field in service dependencies—only `condition` is supported for healthchecks. To fix this, remove every `required: false` line under each dependency in `plugin_daemon.depends_on` so only `condition: service_healthy` remains. For example: ```yaml depends_on: db_postgres: condition: service_healthy db_mysql: condition: service_healthy oceanbase: condition: service_healthy seekdb: condition: service_healthy ``` If your compose file is auto-generated, update the template or `.env.example` and regenerate the file instead of editing it directly. After making these changes, rerun `docker compose up -d` and the error should be resolved. [Reference: Official docker-compose.yaml for Dify v1.10.0](https://github.com/langgenius/dify/blob/bcbd3de33647f308385ce998a92980dfb0d00e6b/docker/docker-compose.yaml#L1-L947) <!-- 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/6f639e60-76f6-4245-a616-fcd4a1b6bf35?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/6f639e60-76f6-4245-a616-fcd4a1b6bf35?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/6f639e60-76f6-4245-a616-fcd4a1b6bf35?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/6f639e60-76f6-4245-a616-fcd4a1b6bf35?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/6f639e60-76f6-4245-a616-fcd4a1b6bf35?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/6f639e60-76f6-4245-a616-fcd4a1b6bf35?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/6f639e60-76f6-4245-a616-fcd4a1b6bf35?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=The%20error%20is%20caused%20by%20the%20unsupported%20%60required%60%20property%20in%20the%20%60depends_on%60%20section%20for%20the%20%60plugin_daemon%60%20service%20in%20your%20docker-compose.yaml.%20Docker%20Compose%20does%20not%20allow%20a%20%60required%60%20field%20in%20service%20dependencies%E2%80%94only%20%60condition%60%20is%20supported%20for%20healthchecks.%20To%20fix%20this%2C%20remove%20every%20%60required%3A%20false%60%20line%20under%20each%20dependency%20in%20%60plugin_daemon.depends_on%60%20so%20only%20%60condition%3A%20service_healthy%60%20remains.%20For%20example%3A%0A%0A%60%60%60yaml%0Adepends_on%3A%0A%20%20db_postgres%3A%0A%20%20%20%20condition%3A%20service_healthy%0A%20%20db_mysql%3A%0A%20%20%20%20condition%3A%20service_healthy%0A%20%20oceanbase%3A%0A%20%20%20%20condition%3A%20service_healthy%0A%20%20seekdb%3A%0A%20%20%20%20condition%3A%20service_healthy%0A%60%60%60%0A%0AIf%20your%20compose%20file%20is%20auto-generated%2C%20update%20the%20template%20or%20%60.env.example%60%20and%20regenerate%20the%20file%20instead%20of%20editing%20it%20directly.%20After%20making%20these%20changes%2C%20rerun%20%60docker%20compose%20up%20-d%60%20and%20the%20error%20should%20be%20resolved.%20%20%0A%5BReference%3A%20Official%20docker-compose.yaml%20for%20Dify%20v1.10.0%5D%28https%3A//github.com/langgenius/dify/blob/bcbd3de33647f308385ce998a92980dfb0d00e6b/docker/docker-compose.yaml%23L1-L947%29)&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/28587)
yindo commented 2026-02-21 20:07:46 -05:00
Author
Owner
Copy Link
Copy Source

@Chenxiuling-Amy commented on GitHub (Nov 24, 2025):

The error is caused by the unsupported required property in the depends_on section for the plugin_daemon service in your docker-compose.yaml. Docker Compose does not allow a required field in service dependencies—only condition is supported for healthchecks. To fix this, remove every required: false line under each dependency in plugin_daemon.depends_on so only condition: service_healthy remains. For example:

depends_on:
db_postgres:
condition: service_healthy
db_mysql:
condition: service_healthy
oceanbase:
condition: service_healthy
seekdb:
condition: service_healthy
If your compose file is auto-generated, update the template or .env.example and regenerate the file instead of editing it directly. After making these changes, rerun docker compose up -d and the error should be resolved. Reference: Official docker-compose.yaml for Dify v1.10.0

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

the docker-compose.yaml is pulled from：https://github.com/langgenius/dify/blob/main/docker/docker-compose.yaml
and so many required properties have to be removed, omg!

@Chenxiuling-Amy commented on GitHub (Nov 24, 2025): > The error is caused by the unsupported `required` property in the `depends_on` section for the `plugin_daemon` service in your docker-compose.yaml. Docker Compose does not allow a `required` field in service dependencies—only `condition` is supported for healthchecks. To fix this, remove every `required: false` line under each dependency in `plugin_daemon.depends_on` so only `condition: service_healthy` remains. For example: > > depends_on: > db_postgres: > condition: service_healthy > db_mysql: > condition: service_healthy > oceanbase: > condition: service_healthy > seekdb: > condition: service_healthy > If your compose file is auto-generated, update the template or `.env.example` and regenerate the file instead of editing it directly. After making these changes, rerun `docker compose up -d` and the error should be resolved. [Reference: Official docker-compose.yaml for Dify v1.10.0](https://github.com/langgenius/dify/blob/bcbd3de33647f308385ce998a92980dfb0d00e6b/docker/docker-compose.yaml#L1-L947) > > _To reply, just mention [@dosu](https://go.dosu.dev/dosubot)._ > > How did I do? [Good](https://app.dosu.dev/response-feedback/6f639e60-76f6-4245-a616-fcd4a1b6bf35?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/6f639e60-76f6-4245-a616-fcd4a1b6bf35?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/6f639e60-76f6-4245-a616-fcd4a1b6bf35?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/6f639e60-76f6-4245-a616-fcd4a1b6bf35?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/6f639e60-76f6-4245-a616-fcd4a1b6bf35?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/6f639e60-76f6-4245-a616-fcd4a1b6bf35?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/6f639e60-76f6-4245-a616-fcd4a1b6bf35?feedback_type=other) > > [![Chat with Dosu](https://camo.githubusercontent.com/7c571478962a6b8a5d47cac74b6824c75e4f6731bba52377e6007f9150462923/68747470733a2f2f646f73752e6465762f646f73752d636861742d62616467652e737667)](https://app.dosu.dev/6088a4f4-073a-43f3-b3d4-4f06fb0c05a0/ask?utm_source=github) [![Open in Cursor](https://camo.githubusercontent.com/bdf7dbded65ee585887f47e5fd6fa099ea0933088b4b03d02e83b4def50154d4/68747470733a2f2f646f73752e6465762f646f73752d696e2d637572736f722e737667)](https://cursor.com/link/prompt?text=The%20error%20is%20caused%20by%20the%20unsupported%20%60required%60%20property%20in%20the%20%60depends_on%60%20section%20for%20the%20%60plugin_daemon%60%20service%20in%20your%20docker-compose.yaml.%20Docker%20Compose%20does%20not%20allow%20a%20%60required%60%20field%20in%20service%20dependencies%E2%80%94only%20%60condition%60%20is%20supported%20for%20healthchecks.%20To%20fix%20this%2C%20remove%20every%20%60required%3A%20false%60%20line%20under%20each%20dependency%20in%20%60plugin_daemon.depends_on%60%20so%20only%20%60condition%3A%20service_healthy%60%20remains.%20For%20example%3A%0A%0A%60%60%60yaml%0Adepends_on%3A%0A%20%20db_postgres%3A%0A%20%20%20%20condition%3A%20service_healthy%0A%20%20db_mysql%3A%0A%20%20%20%20condition%3A%20service_healthy%0A%20%20oceanbase%3A%0A%20%20%20%20condition%3A%20service_healthy%0A%20%20seekdb%3A%0A%20%20%20%20condition%3A%20service_healthy%0A%60%60%60%0A%0AIf%20your%20compose%20file%20is%20auto-generated%2C%20update%20the%20template%20or%20%60.env.example%60%20and%20regenerate%20the%20file%20instead%20of%20editing%20it%20directly.%20After%20making%20these%20changes%2C%20rerun%20%60docker%20compose%20up%20-d%60%20and%20the%20error%20should%20be%20resolved.%20%20%0A%5BReference%3A%20Official%20docker-compose.yaml%20for%20Dify%20v1.10.0%5D%28https%3A//github.com/langgenius/dify/blob/bcbd3de33647f308385ce998a92980dfb0d00e6b/docker/docker-compose.yaml%23L1-L947%29) [![Join Discord](https://camo.githubusercontent.com/7d2066700925db1e370d956834f9ea0e5bc92cecbe84963fbd2a363e45091b4e/68747470733a2f2f696d672e736869656c64732e696f2f62616467652f6a6f696e2d3538363546323f6c6f676f3d646973636f7264266c6f676f436f6c6f723d7768697465266c6162656c3d)](https://go.dosu.dev/discord-bot) [![Share on X](https://camo.githubusercontent.com/a8bd7f3fcf3f5e3bd124eee9ae50ae2ac17b40971726665ac2121d48f9aee155/68747470733a2f2f696d672e736869656c64732e696f2f62616467652f582d73686172652d626c61636b)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/langgenius/dify/issues/28587) the docker-compose.yaml is pulled from：https://github.com/langgenius/dify/blob/main/docker/docker-compose.yaml and so many `required` properties have to be removed, omg!
yindo commented 2026-02-21 20:07:46 -05:00
Author
Owner
Copy Link
Copy Source

@huiyiygy commented on GitHub (Nov 24, 2025):

I have the same problem

@huiyiygy commented on GitHub (Nov 24, 2025): I have the same problem
yindo commented 2026-02-21 20:07:46 -05:00
Author
Owner
Copy Link
Copy Source

@jrgito commented on GitHub (Nov 27, 2025):

me too

@jrgito commented on GitHub (Nov 27, 2025): me too
yindo commented 2026-02-21 20:07:47 -05:00
Author
Owner
Copy Link
Copy Source

@longbingljw commented on GitHub (Dec 2, 2025):

I think you should remove orphan container and update .env.example in dify/docker.Then docker compose up -d.This is a version update ,updating .env.example is a must.

@longbingljw commented on GitHub (Dec 2, 2025): I think you should remove orphan container and update .env.example in dify/docker.Then docker compose up -d.This is a version update ,updating .env.example is a must.
yindo commented 2026-02-21 20:07:47 -05:00
Author
Owner
Copy Link
Copy Source

@longbingljw commented on GitHub (Dec 2, 2025):

'required: false' means docker don't need check services out of your start lists.So it is not a problem.

@longbingljw commented on GitHub (Dec 2, 2025): 'required: false' means docker don't need check services out of your start lists.So it is not a problem.
yindo commented 2026-02-21 20:07:47 -05:00
Author
Owner
Copy Link
Copy Source

@chenyhd commented on GitHub (Dec 9, 2025):

I face the same problem, and it was resolved after I upgraded Docker from version 24.0.4 to version 29.1.2.

@chenyhd commented on GitHub (Dec 9, 2025): I face the same problem, and it was resolved after I upgraded Docker from version 24.0.4 to version 29.1.2.
yindo commented 2026-02-21 20:07:47 -05:00
Author
Owner
Copy Link
Copy Source

@cupertinoleo commented on GitHub (Dec 10, 2025):

please upgrade Docker version

@cupertinoleo commented on GitHub (Dec 10, 2025): please upgrade Docker version
yindo commented 2026-02-21 20:07:47 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Jan 23, 2026):

Hi, @Chenxiuling-Amy. I'm Dosu, and I'm helping the Dify team manage their backlog and am marking this issue as stale.

Issue Summary:

  • You reported a startup error in Dify v1.10.0 self-hosted via Docker due to the unsupported "required" property in the docker-compose.yaml's depends_on section.
  • The issue was clarified that Docker Compose only supports "condition" for service dependencies, and "required: false" lines should be removed.
  • Several users confirmed the problem and shared solutions such as removing orphan containers and updating the .env.example file.
  • The main resolution was removing all "required: false" lines and upgrading Docker to a newer version (e.g., from 24.0.4 to 29.1.2), which fixed the startup error.

Next Steps:

  • Please let me know if this issue is still relevant with the latest version of Dify or your current setup by commenting here.
  • If I don’t hear back within 15 days, I will automatically close this issue.

Thank you for your understanding and contribution!

@dosubot[bot] commented on GitHub (Jan 23, 2026): Hi, @Chenxiuling-Amy. I'm [Dosu](https://dosu.dev), and I'm helping the Dify team manage their backlog and am marking this issue as stale. **Issue Summary:** - You reported a startup error in Dify v1.10.0 self-hosted via Docker due to the unsupported "required" property in the docker-compose.yaml's depends_on section. - The issue was clarified that Docker Compose only supports "condition" for service dependencies, and "required: false" lines should be removed. - Several users confirmed the problem and shared solutions such as removing orphan containers and updating the .env.example file. - The main resolution was removing all "required: false" lines and upgrading Docker to a newer version (e.g., from 24.0.4 to 29.1.2), which fixed the startup error. **Next Steps:** - Please let me know if this issue is still relevant with the latest version of Dify or your current setup by commenting here. - If I don’t hear back within 15 days, I will automatically close this issue. Thank you for your understanding and contribution!
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 stale 🐞 bug
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#20511
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?