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

docker-plugin_daemon-1 Always restarting and reporting errors #12982

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

Originally created by @gentlon on GitHub (Apr 16, 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

docker-plugin_daemon-1 Always restarting and reporting errors：
2025/04/16 06:51:17 main.go:19: [PANIC]Error processing environment variables: envconfig.Process: assigning S3_USE_AWS_MANAGED_IAM to S3UseAwsManagedIam: converting '' to type bool. details: strconv.ParseBool: parsing "": invalid syntax

Image

✔️ Expected Behavior

No response

❌ Actual Behavior

No response

Originally created by @gentlon on GitHub (Apr 16, 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 docker-plugin_daemon-1 Always restarting and reporting errors： 2025/04/16 06:51:17 main.go:19: [PANIC]Error processing environment variables: envconfig.Process: assigning S3_USE_AWS_MANAGED_IAM to S3UseAwsManagedIam: converting '' to type bool. details: strconv.ParseBool: parsing "": invalid syntax ![Image](https://github.com/user-attachments/assets/6ebb91fc-e07d-4950-bd62-539b72ff7cd8) ### ✔️ Expected Behavior _No response_ ### ❌ Actual Behavior _No response_
yindo added the 🐞 bug label 2026-02-21 19:10:00 -05:00
yindo closed this issue 2026-02-21 19:10:00 -05:00
yindo commented 2026-02-21 19:10:01 -05:00
Author
Owner
Copy Link
Copy Source

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

Hello @gentlon! I'm Dosu, your friendly bot here to help you solve bugs, answer questions, and assist with becoming a contributor while you wait for a human maintainer. Let's tackle this issue together!

I found similar threads related to the docker-plugin_daemon-1 container repeatedly restarting due to issues with the S3_USE_AWS_MANAGED_IAM environment variable. One such issue was resolved by ensuring that the environment variable is correctly set in both the .env file and the docker-compose.yaml file [1].

To resolve this issue, you can follow these steps:

  1. In your .env file, explicitly set the following variables:

    PLUGIN_S3_USE_AWS_MANAGED_IAM=false
PLUGIN_S3_USE_PATH_STYLE=false

  2. In your docker-compose.yaml file, ensure the environment variable is set with a default value:

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

These configurations ensure that the boolean variable is properly set and parsed, preventing the 'invalid syntax' error and stopping the container from restarting due to a strconv.ParseBool failure [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 16, 2025): <!-- Greeting --> Hello @gentlon! I'm [Dosu](https://dosu.dev), your friendly bot here to help you solve bugs, answer questions, and assist with becoming a contributor while you wait for a human maintainer. Let's tackle this issue together! <!-- Answer --> I found similar threads related to the `docker-plugin_daemon-1` container repeatedly restarting due to issues with the `S3_USE_AWS_MANAGED_IAM` environment variable. One such issue was resolved by ensuring that the environment variable is correctly set in both the `.env` file and the `docker-compose.yaml` file <sup>[[1]](https://github.com/langgenius/dify/issues/17703)</sup>. To resolve this issue, you can follow these steps: 1. In your `.env` file, explicitly set the following variables: ```properties PLUGIN_S3_USE_AWS_MANAGED_IAM=false PLUGIN_S3_USE_PATH_STYLE=false ``` 2. In your `docker-compose.yaml` file, ensure the environment variable is set with a default value: ```yaml plugin_daemon: environment: S3_USE_AWS_MANAGED_IAM: ${PLUGIN_S3_USE_AWS_MANAGED_IAM:-false} ``` These configurations ensure that the boolean variable is properly set and parsed, preventing the 'invalid syntax' error and stopping the container from restarting due to a `strconv.ParseBool` failure <sup>[[2]](https://github.com/langgenius/dify/issues/17677)</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/ece49cb8-3a45-48d4-a0b6-ad8a49a8690c?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/ece49cb8-3a45-48d4-a0b6-ad8a49a8690c?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/ece49cb8-3a45-48d4-a0b6-ad8a49a8690c?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/ece49cb8-3a45-48d4-a0b6-ad8a49a8690c?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/ece49cb8-3a45-48d4-a0b6-ad8a49a8690c?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/ece49cb8-3a45-48d4-a0b6-ad8a49a8690c?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/ece49cb8-3a45-48d4-a0b6-ad8a49a8690c?feedback_type=other)</sup>
yindo commented 2026-02-21 19:10:01 -05:00
Author
Owner
Copy Link
Copy Source

@gentlon commented on GitHub (Apr 16, 2025):

@dosu First of all, thank you for answering my question，I set the relevant parameters in your way, but after restarting, I still reported the same error；
My two configuration files are as follows：

Image

Image

Image

@gentlon commented on GitHub (Apr 16, 2025): @dosu First of all, thank you for answering my question，I set the relevant parameters in your way, but after restarting, I still reported the same error； My two configuration files are as follows： ![Image](https://github.com/user-attachments/assets/47ef62d1-e993-4807-b8c2-303de1271818) ![Image](https://github.com/user-attachments/assets/614fd55d-32e4-467c-9689-995ff3ffbba2) ![Image](https://github.com/user-attachments/assets/4a95368a-19f0-479c-a67f-ce6ff7f7be30)
yindo commented 2026-02-21 19:10:01 -05:00
Author
Owner
Copy Link
Copy Source

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

Ensure that the environment variable PLUGIN_S3_USE_AWS_MANAGED_IAM is set correctly in your .env file and referenced properly in your docker-compose.yaml file. Here’s what you should do:

  1. In your .env file, make sure you have:

    PLUGIN_S3_USE_AWS_MANAGED_IAM=false

  2. In your docker-compose.yaml file, ensure the environment variable is set with a default value:

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

Double-check that there are no typos or missing entries in both files. If the issue persists, verify that the .env file is being correctly loaded by Docker Compose. You can do this by checking if other environment variables from the .env file are being applied as expected. If necessary, try explicitly passing the .env file to Docker Compose using the --env-file option.

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 16, 2025): <!-- Answer --> Ensure that the environment variable `PLUGIN_S3_USE_AWS_MANAGED_IAM` is set correctly in your `.env` file and referenced properly in your `docker-compose.yaml` file. Here’s what you should do: 1. In your `.env` file, make sure you have: ```properties PLUGIN_S3_USE_AWS_MANAGED_IAM=false ``` 2. In your `docker-compose.yaml` file, ensure the environment variable is set with a default value: ```yaml plugin_daemon: environment: S3_USE_AWS_MANAGED_IAM: ${PLUGIN_S3_USE_AWS_MANAGED_IAM:-false} ``` Double-check that there are no typos or missing entries in both files. If the issue persists, verify that the `.env` file is being correctly loaded by Docker Compose. You can do this by checking if other environment variables from the `.env` file are being applied as expected. If necessary, try explicitly passing the `.env` file to Docker Compose using the `--env-file` option. <!-- 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/b1f5278f-91ee-42fd-b078-d24844d14eff?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/b1f5278f-91ee-42fd-b078-d24844d14eff?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/b1f5278f-91ee-42fd-b078-d24844d14eff?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/b1f5278f-91ee-42fd-b078-d24844d14eff?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/b1f5278f-91ee-42fd-b078-d24844d14eff?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/b1f5278f-91ee-42fd-b078-d24844d14eff?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/b1f5278f-91ee-42fd-b078-d24844d14eff?feedback_type=other)</sup>
yindo commented 2026-02-21 19:10:01 -05:00
Author
Owner
Copy Link
Copy Source

@gentlon commented on GitHub (Apr 16, 2025):

@dosu Okay, I'll try again

@gentlon commented on GitHub (Apr 16, 2025): @dosu Okay, I'll try again
yindo commented 2026-02-21 19:10:01 -05:00
Author
Owner
Copy Link
Copy Source

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

Hey @gentlon! I'm here to help with technical questions, bug fixes, and engineering knowledge. If you have any issues or need further assistance, feel free to ask! If you think I should have answered this request, you can reach out to the Dosu Team. 😊

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 16, 2025): <!-- Answer --> Hey @gentlon! I'm here to help with technical questions, bug fixes, and engineering knowledge. If you have any issues or need further assistance, feel free to ask! If you think I should have answered this request, you can reach out to the [Dosu Team](mailto:customersuccess@dosu.dev). 😊 <!-- 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/a637d798-742d-4261-bad8-0de92071527b?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/a637d798-742d-4261-bad8-0de92071527b?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/a637d798-742d-4261-bad8-0de92071527b?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/a637d798-742d-4261-bad8-0de92071527b?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/a637d798-742d-4261-bad8-0de92071527b?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/a637d798-742d-4261-bad8-0de92071527b?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/a637d798-742d-4261-bad8-0de92071527b?feedback_type=other)</sup>
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
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#12982
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?