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

Build devContainer error when the network is normal #12543

New Issue
Closed
opened 2026-02-21 19:07:55 -05:00 by yindo · 1 comment
yindo commented 2026-02-21 19:07:55 -05:00
Owner
Copy Link
Copy Source

Originally created by @441126098 on GitHub (Apr 4, 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.1.3

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

When attempting to build the devContainer on macOS, an error occurs during the process. This seems similar to an issue discussed in Discussion #17238, where the user used FastGithub in a WSL environment and encountered connectivity problems when downloading dependencies.
However, after modifying the devcontainer.json configuration file and setting the dockerDashComposeVersion field to v2.24.5, the container was able to build successfully. This suggests that the default Docker Compose version might be incompatible or unstable in the current environment setup.

To Reproduce：

  1. Clone the Dify repo on macOS.
  2. Open it in VS Code with Dev Containers extension installed.
  3. Rebuild and reopen in container.
  4. Wait for the image to be built.

Environment
• OS: macOS (version: 15.3.2 (24D81))
• Docker Desktop: 4.40.0
• VS Code: 1.98.2
• DevContainer: Default from repository

✔️ Expected Behavior

The devContainer should rebuild successfully with access to GitHub-hosted resources.

❌ Actual Behavior

Build fails with an error while trying to download from https://github.com/docker/compose/.The following is the error message.
452.0 fatal: unable to access 'https://github.com/docker/compose/': HTTP/2 stream 1 was not closed cleanly before end of the underlying stream
452.0 (!) Invalid compose_version value: 2\nValid values:\n
452.0 ERROR: Feature "Docker (Docker-in-Docker)" (ghcr.io/devcontainers/features/docker-in-docker) failed to install! Look at the documentation at https://github.com/devcontainers/features/tree/main/src/docker-in-docker for help troubleshooting this error.

Originally created by @441126098 on GitHub (Apr 4, 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.1.3 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce When attempting to build the devContainer on macOS, an error occurs during the process. This seems similar to an issue discussed in [Discussion #17238](https://github.com/langgenius/dify/discussions/17238), where the user used FastGithub in a WSL environment and encountered connectivity problems when downloading dependencies. However, after modifying the devcontainer.json configuration file and setting the dockerDashComposeVersion field to v2.24.5, the container was able to build successfully. This suggests that the default Docker Compose version might be incompatible or unstable in the current environment setup. To Reproduce： 1. Clone the Dify repo on macOS. 2. Open it in VS Code with Dev Containers extension installed. 3. Rebuild and reopen in container. 4. Wait for the image to be built. Environment • OS: macOS (version: 15.3.2 (24D81)) • Docker Desktop: 4.40.0 • VS Code: 1.98.2 • DevContainer: Default from repository ### ✔️ Expected Behavior The devContainer should rebuild successfully with access to GitHub-hosted resources. ### ❌ Actual Behavior Build fails with an error while trying to download from https://github.com/docker/compose/.The following is the error message. 452.0 fatal: unable to access 'https://github.com/docker/compose/': HTTP/2 stream 1 was not closed cleanly before end of the underlying stream 452.0 (!) Invalid compose_version value: 2\nValid values:\n 452.0 ERROR: Feature "Docker (Docker-in-Docker)" (ghcr.io/devcontainers/features/docker-in-docker) failed to install! Look at the documentation at https://github.com/devcontainers/features/tree/main/src/docker-in-docker for help troubleshooting this error.
yindo added the 🙏 help wanted label 2026-02-21 19:07:55 -05:00
yindo closed this issue 2026-02-21 19:07:55 -05:00
yindo commented 2026-02-21 19:07:55 -05:00
Author
Owner
Copy Link
Copy Source

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

Hello @441126098! I'm Dosu, your friendly bot here to help you with bugs, questions, and becoming a contributor. I'll assist you while we wait for a human maintainer to join the conversation. Let's get started!

A similar issue was discussed in Discussion #17238, where the user resolved the problem by modifying the devcontainer.json configuration file and setting the dockerDashComposeVersion field to v2.24.5. This suggests that the default Docker Compose version might be incompatible or unstable in your current environment setup [1].

To address the build error, try the following steps:

  1. Modify your devcontainer.json file to specify the Docker Compose version as v2.24.5.
  2. Ensure that your Docker Desktop is configured to use at least 2 virtual CPUs and 8GB of initial memory, as recommended for macOS [2].

These adjustments should help resolve the compatibility issues and allow the devContainer to build successfully.

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 4, 2025): <!-- Greeting --> Hello @441126098! I'm [Dosu](https://dosu.dev), your friendly bot here to help you with bugs, questions, and becoming a contributor. I'll assist you while we wait for a human maintainer to join the conversation. Let's get started! <!-- Answer --> A similar issue was discussed in [Discussion #17238](https://github.com/langgenius/dify/discussions/17238), where the user resolved the problem by modifying the `devcontainer.json` configuration file and setting the `dockerDashComposeVersion` field to `v2.24.5`. This suggests that the default Docker Compose version might be incompatible or unstable in your current environment setup <sup>[[1]](https://github.com/langgenius/dify/discussions/17238)</sup>. To address the build error, try the following steps: 1. Modify your `devcontainer.json` file to specify the Docker Compose version as `v2.24.5`. 2. Ensure that your Docker Desktop is configured to use at least 2 virtual CPUs and 8GB of initial memory, as recommended for macOS <sup>[[2]](https://github.com/langgenius/dify-docs/blob/main/lang-check/commit-79f79-0214.txt)</sup>. These adjustments should help resolve the compatibility issues and allow the devContainer to build successfully. <!-- 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/0659ff3d-066f-45f9-981e-fb385c69b27f?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/0659ff3d-066f-45f9-981e-fb385c69b27f?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/0659ff3d-066f-45f9-981e-fb385c69b27f?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/0659ff3d-066f-45f9-981e-fb385c69b27f?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/0659ff3d-066f-45f9-981e-fb385c69b27f?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/0659ff3d-066f-45f9-981e-fb385c69b27f?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/0659ff3d-066f-45f9-981e-fb385c69b27f?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 🙏 help wanted
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#12543
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?