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

Whenever I start docker, plugin_daemon restarts repeatedly #13144

New Issue
Closed
opened 2026-02-21 19:10:45 -05:00 by yindo · 5 comments
yindo commented 2026-02-21 19:10:45 -05:00
Owner
Copy Link
Copy Source

Originally created by @Shanshuimei on GitHub (Apr 19, 2025).

Self Checks

  • 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 (我已阅读并同意 Language Policy).
  • [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:)
  • Please do not modify this template :) and fill in all the required fields.

Dify version

1.2.0

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

  1. Start Docker
  2. plugin_daemon restarts repeatedly
  3. Edit .env
    Image
  4. Edit docker-compose.yaml
    Image
  5. Restart Docker

✔️ Expected Behavior

No error

❌ Actual Behavior

Image

Originally created by @Shanshuimei on GitHub (Apr 19, 2025). ### Self Checks - [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 (我已阅读并同意 [Language Policy](https://github.com/langgenius/dify/issues/1542)). - [x] [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:) - [x] Please do not modify this template :) and fill in all the required fields. ### Dify version 1.2.0 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce 1. Start Docker 2. plugin_daemon restarts repeatedly 3. Edit .env ![Image](https://github.com/user-attachments/assets/0043179f-9b19-4152-b33a-a8fdba8643e2) 4. Edit docker-compose.yaml ![Image](https://github.com/user-attachments/assets/0f653625-077c-42e5-80e8-a2e0a04686f8) 5. Restart Docker ### ✔️ Expected Behavior No error ### ❌ Actual Behavior ![Image](https://github.com/user-attachments/assets/7f01738f-462d-4932-85de-cf5b0e07d666)
yindo closed this issue 2026-02-21 19:10:45 -05:00
yindo commented 2026-02-21 19:10:45 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Apr 19, 2025):

Hello @Shanshuimei! I'm Dosu, your friendly bot here to help you tackle bugs, answer your questions, and navigate the world of contributions while we wait for a human maintainer. Let's get started!

I found a similar issue that was resolved. The problem with the plugin_daemon restarting repeatedly is often related to the S3_USE_AWS_MANAGED_IAM environment variable not being set correctly. Here's how you can resolve it:

  1. Ensure that the environment variable is explicitly set in your .env file:

    PLUGIN_S3_USE_AWS_MANAGED_IAM=false
PLUGIN_S3_USE_PATH_STYLE=false

  2. Modify your docker-compose.yaml file to include a default value for the environment variable:

    plugin_daemon:
  environment:
    S3_USE_AWS_MANAGED_IAM: ${PLUGIN_S3_USE_AWS_MANAGED_IAM:-false}

These steps should help prevent the error by ensuring the variable is correctly interpreted as a boolean, thus stopping the plugin_daemon from restarting repeatedly [1][2].

To continue talking to Dosu, mention @dosu.

Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other

@dosubot[bot] commented on GitHub (Apr 19, 2025): <!-- Greeting --> Hello @Shanshuimei! I'm [Dosu](https://dosu.dev), your friendly bot here to help you tackle bugs, answer your questions, and navigate the world of contributions while we wait for a human maintainer. Let's get started! <!-- Answer --> I found a similar issue that was resolved. The problem with the `plugin_daemon` restarting repeatedly is often related to the `S3_USE_AWS_MANAGED_IAM` environment variable not being set correctly. Here's how you can resolve it: 1. Ensure that the environment variable is explicitly set in your `.env` file: ```properties PLUGIN_S3_USE_AWS_MANAGED_IAM=false PLUGIN_S3_USE_PATH_STYLE=false ``` 2. Modify your `docker-compose.yaml` file to include a default value for the environment variable: ```yaml plugin_daemon: environment: S3_USE_AWS_MANAGED_IAM: ${PLUGIN_S3_USE_AWS_MANAGED_IAM:-false} ``` These steps should help prevent the error by ensuring the variable is correctly interpreted as a boolean, thus stopping the `plugin_daemon` from restarting repeatedly <sup>[[1]](https://github.com/langgenius/dify/issues/17703)</sup><sup>[[2]](https://github.com/langgenius/dify/issues/18122)</sup>. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.* --- <sup>Help Dosu learn! Give it feedback: [Great Response](https://app.dosu.dev/response-feedback/eafbfe9f-622c-43ab-b77e-66c3f13b977a?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/eafbfe9f-622c-43ab-b77e-66c3f13b977a?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/eafbfe9f-622c-43ab-b77e-66c3f13b977a?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/eafbfe9f-622c-43ab-b77e-66c3f13b977a?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/eafbfe9f-622c-43ab-b77e-66c3f13b977a?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/eafbfe9f-622c-43ab-b77e-66c3f13b977a?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/eafbfe9f-622c-43ab-b77e-66c3f13b977a?feedback_type=other)</sup>
yindo commented 2026-02-21 19:10:45 -05:00
Author
Owner
Copy Link
Copy Source

@Shanshuimei commented on GitHub (Apr 20, 2025):

Hello @Shanshuimei! I'm Dosu, your friendly bot here to help you tackle bugs, answer your questions, and navigate the world of contributions while we wait for a human maintainer. Let's get started!

I found a similar issue that was resolved. The problem with the plugin_daemon restarting repeatedly is often related to the S3_USE_AWS_MANAGED_IAM environment variable not being set correctly. Here's how you can resolve it:

  1. Ensure that the environment variable is explicitly set in your .env file:
    PLUGIN_S3_USE_AWS_MANAGED_IAM=false
    PLUGIN_S3_USE_PATH_STYLE=false
  2. Modify your docker-compose.yaml file to include a default value for the environment variable:
    plugin_daemon:
    environment:
    S3_USE_AWS_MANAGED_IAM: ${PLUGIN_S3_USE_AWS_MANAGED_IAM:-false}

These steps should help prevent the error by ensuring the variable is correctly interpreted as a boolean, thus stopping the plugin_daemon from restarting repeatedly [1][2].

To continue talking to Dosu, mention @dosu.

Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other

@dosu Thanks, robot, but it doesn't work for me. 😢

@Shanshuimei commented on GitHub (Apr 20, 2025): > Hello [@Shanshuimei](https://github.com/Shanshuimei)! I'm [Dosu](https://dosu.dev), your friendly bot here to help you tackle bugs, answer your questions, and navigate the world of contributions while we wait for a human maintainer. Let's get started! > > I found a similar issue that was resolved. The problem with the `plugin_daemon` restarting repeatedly is often related to the `S3_USE_AWS_MANAGED_IAM` environment variable not being set correctly. Here's how you can resolve it: > > 1. Ensure that the environment variable is explicitly set in your `.env` file: > PLUGIN_S3_USE_AWS_MANAGED_IAM=false > PLUGIN_S3_USE_PATH_STYLE=false > 2. Modify your `docker-compose.yaml` file to include a default value for the environment variable: > plugin_daemon: > environment: > S3_USE_AWS_MANAGED_IAM: ${PLUGIN_S3_USE_AWS_MANAGED_IAM:-false} > > These steps should help prevent the error by ensuring the variable is correctly interpreted as a boolean, thus stopping the `plugin_daemon` from restarting repeatedly [[1]](https://github.com/langgenius/dify/issues/17703)[[2]](https://github.com/langgenius/dify/issues/18122). > > _To continue talking to [Dosu](https://dosu.dev), mention [@dosu](https://github.com/dosu)._ > > Help Dosu learn! Give it feedback: [Great Response](https://app.dosu.dev/response-feedback/eafbfe9f-622c-43ab-b77e-66c3f13b977a?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/eafbfe9f-622c-43ab-b77e-66c3f13b977a?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/eafbfe9f-622c-43ab-b77e-66c3f13b977a?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/eafbfe9f-622c-43ab-b77e-66c3f13b977a?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/eafbfe9f-622c-43ab-b77e-66c3f13b977a?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/eafbfe9f-622c-43ab-b77e-66c3f13b977a?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/eafbfe9f-622c-43ab-b77e-66c3f13b977a?feedback_type=other) @dosu Thanks, robot, but it doesn't work for me. 😢
yindo commented 2026-02-21 19:10:45 -05:00
Author
Owner
Copy Link
Copy Source

@zzy127-bit commented on GitHub (Apr 20, 2025):

Thanks, this solved the issue and was very helpful!"

@zzy127-bit commented on GitHub (Apr 20, 2025): Thanks, this solved the issue and was very helpful!"
yindo commented 2026-02-21 19:10:45 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Apr 20, 2025):

To resolve the issue with the plugin_daemon restarting repeatedly, ensure that both S3_USE_AWS_MANAGED_IAM and S3_USE_PATH_STYLE environment variables have default values set. Here's what you can do:

  1. Add the following to your .env file:

    PLUGIN_S3_USE_AWS_MANAGED_IAM=false
PLUGIN_S3_USE_PATH_STYLE=false

  2. Update your docker-compose.yaml file to include default values for both variables:

    plugin_daemon:
  environment:
    S3_USE_AWS_MANAGED_IAM: ${PLUGIN_S3_USE_AWS_MANAGED_IAM:-false}
    S3_USE_PATH_STYLE: ${PLUGIN_S3_USE_PATH_STYLE:-false}

After making these changes, remove the existing containers and restart the application:

  1. Stop and remove existing containers:

    docker compose down

  2. Remove the images:

    docker rmi $(docker images -q 'dify-*')

  3. Pull and start fresh containers:

    docker compose up -d

These steps should help resolve the issue by ensuring the environment variables are correctly interpreted [1][2].

To continue talking to Dosu, mention @dosu.

Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other

@dosubot[bot] commented on GitHub (Apr 20, 2025): <!-- Answer --> To resolve the issue with the `plugin_daemon` restarting repeatedly, ensure that both `S3_USE_AWS_MANAGED_IAM` and `S3_USE_PATH_STYLE` environment variables have default values set. Here's what you can do: 1. Add the following to your `.env` file: ```plaintext PLUGIN_S3_USE_AWS_MANAGED_IAM=false PLUGIN_S3_USE_PATH_STYLE=false ``` 2. Update your `docker-compose.yaml` file to include default values for both variables: ```yaml plugin_daemon: environment: S3_USE_AWS_MANAGED_IAM: ${PLUGIN_S3_USE_AWS_MANAGED_IAM:-false} S3_USE_PATH_STYLE: ${PLUGIN_S3_USE_PATH_STYLE:-false} ``` After making these changes, remove the existing containers and restart the application: 1. Stop and remove existing containers: ```bash docker compose down ``` 2. Remove the images: ```bash docker rmi $(docker images -q 'dify-*') ``` 3. Pull and start fresh containers: ```bash docker compose up -d ``` These steps should help resolve the issue by ensuring the environment variables are correctly interpreted <sup>[[1]](https://github.com/langgenius/dify/issues/17786)</sup><sup>[[2]](https://github.com/langgenius/dify/issues/18010)</sup>. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.* --- <sup>Help Dosu learn! Give it feedback: [Great Response](https://app.dosu.dev/response-feedback/9bdeb0f0-f371-4b4f-98e4-04790d656872?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/9bdeb0f0-f371-4b4f-98e4-04790d656872?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/9bdeb0f0-f371-4b4f-98e4-04790d656872?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/9bdeb0f0-f371-4b4f-98e4-04790d656872?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/9bdeb0f0-f371-4b4f-98e4-04790d656872?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/9bdeb0f0-f371-4b4f-98e4-04790d656872?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/9bdeb0f0-f371-4b4f-98e4-04790d656872?feedback_type=other)</sup>
yindo commented 2026-02-21 19:10:45 -05:00
Author
Owner
Copy Link
Copy Source

@Shanshuimei commented on GitHub (Apr 20, 2025):

To resolve the issue with the plugin_daemon restarting repeatedly, ensure that both S3_USE_AWS_MANAGED_IAM and S3_USE_PATH_STYLE environment variables have default values set. Here's what you can do:

  1. Add the following to your .env file: 
    PLUGIN_S3_USE_AWS_MANAGED_IAM=false
PLUGIN_S3_USE_PATH_STYLE=false
  2. Update your docker-compose.yaml file to include default values for both variables:
    plugin_daemon:
    environment:
    S3_USE_AWS_MANAGED_IAM: ${PLUGIN_S3_USE_AWS_MANAGED_IAM:-false}
    S3_USE_PATH_STYLE: ${PLUGIN_S3_USE_PATH_STYLE:-false}

After making these changes, remove the existing containers and restart the application:

  1. Stop and remove existing containers:
    docker compose down
  2. Remove the images:
    docker rmi $(docker images -q 'dify-*')
  3. Pull and start fresh containers:
    docker compose up -d

These steps should help resolve the issue by ensuring the environment variables are correctly interpreted [1][2].

To continue talking to Dosu, mention @dosu.

Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other

Thank you, Dosu! It works! 😚

@Shanshuimei commented on GitHub (Apr 20, 2025): > To resolve the issue with the `plugin_daemon` restarting repeatedly, ensure that both `S3_USE_AWS_MANAGED_IAM` and `S3_USE_PATH_STYLE` environment variables have default values set. Here's what you can do: > > 1. Add the following to your `.env` file: > ``` > PLUGIN_S3_USE_AWS_MANAGED_IAM=false > PLUGIN_S3_USE_PATH_STYLE=false > ``` > 2. Update your `docker-compose.yaml` file to include default values for both variables: > plugin_daemon: > environment: > S3_USE_AWS_MANAGED_IAM: ${PLUGIN_S3_USE_AWS_MANAGED_IAM:-false} > S3_USE_PATH_STYLE: ${PLUGIN_S3_USE_PATH_STYLE:-false} > > After making these changes, remove the existing containers and restart the application: > > 1. Stop and remove existing containers: > docker compose down > 2. Remove the images: > docker rmi $(docker images -q 'dify-*') > 3. Pull and start fresh containers: > docker compose up -d > > These steps should help resolve the issue by ensuring the environment variables are correctly interpreted [[1]](https://github.com/langgenius/dify/issues/17786)[[2]](https://github.com/langgenius/dify/issues/18010). > > _To continue talking to [Dosu](https://dosu.dev), mention [@dosu](https://github.com/dosu)._ > > Help Dosu learn! Give it feedback: [Great Response](https://app.dosu.dev/response-feedback/9bdeb0f0-f371-4b4f-98e4-04790d656872?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/9bdeb0f0-f371-4b4f-98e4-04790d656872?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/9bdeb0f0-f371-4b4f-98e4-04790d656872?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/9bdeb0f0-f371-4b4f-98e4-04790d656872?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/9bdeb0f0-f371-4b4f-98e4-04790d656872?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/9bdeb0f0-f371-4b4f-98e4-04790d656872?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/9bdeb0f0-f371-4b4f-98e4-04790d656872?feedback_type=other) Thank you, Dosu! It works! 😚
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
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#13144
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?