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

Starting the backend API module dependencies' containers on MacOS may result in container startup failure due to file permission issues. #2451

New Issue
Closed
opened 2026-02-21 17:45:55 -05:00 by yindo · 0 comments
yindo commented 2026-02-21 17:45:55 -05:00
Owner
Copy Link
Copy Source

Originally created by @wang14597 on GitHub (Apr 23, 2024).

Self Checks

  • I have searched for existing issues search for existing issues, including closed ones.
  • I confirm that I am using English to submit report (我已阅读并同意 Language Policy).
  • Pleas do not modify this template :) and fill in all the required fields.

Provide a description of requested docs changes

When run the command docker-compose -f docker-compose.middleware.yaml -p dify up -d on macOS, the containers might fail to start.
image
Then I granted permissions to the relevant files, and the command could be executed normally. However, when I checked the contents of the container, I found that the container failed to start.
image
image

It is because that macOS has stricter security restrictions on the file system, especially when Docker attempts to modify permissions on mounted volume directories.

I would like to resolve this issue, please approve.

Thank you!

Originally created by @wang14597 on GitHub (Apr 23, 2024). ### 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 report (我已阅读并同意 [Language Policy](https://github.com/langgenius/dify/issues/1542)). - [X] Pleas do not modify this template :) and fill in all the required fields. ### Provide a description of requested docs changes When run the command `docker-compose -f docker-compose.middleware.yaml -p dify up -d` on macOS, the containers might fail to start. ![image](https://github.com/langgenius/dify/assets/81572468/d342a24f-2a9f-4823-9508-8434d3fa4fee) Then I granted permissions to the relevant files, and the command could be executed normally. However, when I checked the contents of the container, I found that the container failed to start. ![image](https://github.com/langgenius/dify/assets/81572468/71450536-9f2a-4c9c-b5ed-89ca010f0e54) ![image](https://github.com/langgenius/dify/assets/81572468/37dacda7-f802-4af8-8836-0e5d15749e3e) It is because that macOS has stricter security restrictions on the file system, especially when Docker attempts to modify permissions on mounted volume directories. I would like to resolve this issue, please approve. Thank you!
yindo added the 🐞 bug label 2026-02-21 17:45:55 -05:00
yindo closed this issue 2026-02-21 17:45:55 -05:00
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#2451
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?