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

Should we add a default value of MAX_LIFETIME_SECONDS to the unstructured docker container in docker compose file #5224

New Issue
Closed
opened 2026-02-21 18:09:57 -05:00 by yindo · 1 comment
yindo commented 2026-02-21 18:09:57 -05:00
Owner
Copy Link
Copy Source

Originally created by @CXwudi on GitHub (Aug 26, 2024).

Originally assigned to: @JohnJyong on GitHub.

Self Checks

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

1. Is this request related to a challenge you're experiencing? Tell me about your story.

If you self-host Unstructured, you might experience memory leak issue from https://github.com/Unstructured-IO/unstructured-api/issues/197

Fortunately, based on the dev's reply and the README. You can set MAX_LIFETIME_SECONDS to some value to shut down the server to work around the memory leak issue with restart=always docker flag.

Hence, I am wondering, should we add MAX_LIFETIME_SECONDS to the docker compose file? If not, maybe shall we mention the memory leak issue in a documentation or a comment in the docker compose file to let the user aware?

2. Additional context or comments

No response

3. Can you help us with this feature?

  • I am interested in contributing to this feature.
Originally created by @CXwudi on GitHub (Aug 26, 2024). Originally assigned to: @JohnJyong on GitHub. ### Self Checks - [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. ### 1. Is this request related to a challenge you're experiencing? Tell me about your story. If you self-host Unstructured, you might experience memory leak issue from https://github.com/Unstructured-IO/unstructured-api/issues/197 Fortunately, based on the [dev's reply](https://github.com/Unstructured-IO/unstructured-api/issues/197#issuecomment-2311136573) and the [README](https://github.com/Unstructured-IO/unstructured-api?tab=readme-ov-file#controlling-server-life-time). You can set `MAX_LIFETIME_SECONDS` to some value to shut down the server to work around the memory leak issue with `restart=always` docker flag. Hence, I am wondering, should we add `MAX_LIFETIME_SECONDS` to the docker compose file? If not, maybe shall we mention the memory leak issue in a documentation or a comment in the docker compose file to let the user aware? ### 2. Additional context or comments _No response_ ### 3. Can you help us with this feature? - [ ] I am interested in contributing to this feature.
yindo added the 📚 documentation label 2026-02-21 18:09:57 -05:00
yindo closed this issue 2026-02-21 18:09:57 -05:00
yindo commented 2026-02-21 18:09:57 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Aug 26, 2024):

Hence, I am wondering, should we add MAX_LIFETIME_SECONDS to the docker compose file? If not, maybe shall we mention the memory leak issue in a documentation or a comment in the docker compose file to let the user aware?

Thanks for the suggestion, I will add it later.

@crazywoola commented on GitHub (Aug 26, 2024): > Hence, I am wondering, should we add MAX_LIFETIME_SECONDS to the docker compose file? If not, maybe shall we mention the memory leak issue in a documentation or a comment in the docker compose file to let the user aware? Thanks for the suggestion, I will add it later.
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 📚 documentation
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#5224
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?