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

Error response from daemon: Get "https://registry-1.docker.io/v2/": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers) #5792

New Issue
Closed
opened 2026-02-21 18:12:37 -05:00 by yindo · 2 comments
yindo commented 2026-02-21 18:12:37 -05:00
Owner
Copy Link
Copy Source

Originally created by @GreatAsia on GitHub (Sep 25, 2024).

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

0.8.3

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

docker compose up -d

✔️ Expected Behavior

down load images and start servers

❌ Actual Behavior

WARN[0000] The "CERTBOT_EMAIL" variable is not set. Defaulting to a blank string.
WARN[0000] The "CERTBOT_DOMAIN" variable is not set. Defaulting to a blank string.
[+] Running 0/5
⠿ worker Error 15.0s
⠿ sandbox Error 15.0s
⠿ ssrf_proxy Error 15.0s
⠿ web Error 15.0s
⠿ api Error 15.0s
Error response from daemon: Get "https://registry-1.docker.io/v2/": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)

Originally created by @GreatAsia on GitHub (Sep 25, 2024). ### 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 0.8.3 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce docker compose up -d ### ✔️ Expected Behavior down load images and start servers ### ❌ Actual Behavior WARN[0000] The "CERTBOT_EMAIL" variable is not set. Defaulting to a blank string. WARN[0000] The "CERTBOT_DOMAIN" variable is not set. Defaulting to a blank string. [+] Running 0/5 ⠿ worker Error 15.0s ⠿ sandbox Error 15.0s ⠿ ssrf_proxy Error 15.0s ⠿ web Error 15.0s ⠿ api Error 15.0s Error response from daemon: Get "https://registry-1.docker.io/v2/": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
yindo added the 🐞 bug label 2026-02-21 18:12:37 -05:00
yindo closed this issue 2026-02-21 18:12:37 -05:00
yindo commented 2026-02-21 18:12:37 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Sep 25, 2024):

Hello @GreatAsia! I'm here to help you with any bugs, questions, or contributions. Let's work together to resolve the issue you're facing.

I found some similar issues and discussions that might be relevant to your problem:

  1. connection error: request error, status_code: 503 (open) [1]
  2. Unable to use external HTTP requests after installing Dify with docker-compose on Ubuntu (open) [2]
  3. connection error when set up model provider (open) [3]

For your specific issue, it seems like there might be a network configuration or firewall setting blocking the connection to Docker Hub. Here are a few steps you can try to resolve this:

  1. Check Network Configuration: Ensure that your network allows outbound HTTPS connections to registry-1.docker.io. This might involve checking firewall settings or proxy configurations.

  2. Increase Timeout: You can try increasing the Docker client timeout by setting the DOCKER_CLIENT_TIMEOUT and COMPOSE_HTTP_TIMEOUT environment variables:

    export DOCKER_CLIENT_TIMEOUT=300
export COMPOSE_HTTP_TIMEOUT=300

  3. Check Docker Daemon Logs: Inspect the Docker daemon logs for more detailed error messages:

    sudo journalctl -u docker.service

  4. Update Docker: Ensure you are using a compatible Docker version. For Dify, Docker 19.03 or later is recommended [4].

  5. DNS Issues: Sometimes DNS resolution issues can cause such errors. You can try changing the DNS server in your Docker daemon configuration (/etc/docker/daemon.json):

    {
  "dns": ["8.8.8.8", "8.8.4.4"]
}

    Then restart the Docker service:

    sudo systemctl restart docker

If these steps do not resolve the issue, you might want to look into the detailed environment configuration guide for Dify in a Docker setup [5][6].

To continue talking to Dosu, mention @dosu.

@dosubot[bot] commented on GitHub (Sep 25, 2024): <!-- Greeting --> Hello @GreatAsia! I'm here to help you with any bugs, questions, or contributions. Let's work together to resolve the issue you're facing. <!-- Answer --> I found some similar issues and discussions that might be relevant to your problem: 1. [connection error: request error, status_code: 503](https://github.com/langgenius/dify/discussions/6181) (open) <sup>[[1]](https://github.com/langgenius/dify/discussions/6181)</sup> 2. [Unable to use external HTTP requests after installing Dify with docker-compose on Ubuntu](https://github.com/langgenius/dify/discussions/8423) (open) <sup>[[2]](https://github.com/langgenius/dify/discussions/8423)</sup> 3. [connection error when set up model provider](https://github.com/langgenius/dify/discussions/7839) (open) <sup>[[3]](https://github.com/langgenius/dify/discussions/7839)</sup> For your specific issue, it seems like there might be a network configuration or firewall setting blocking the connection to Docker Hub. Here are a few steps you can try to resolve this: 1. **Check Network Configuration**: Ensure that your network allows outbound HTTPS connections to `registry-1.docker.io`. This might involve checking firewall settings or proxy configurations. 2. **Increase Timeout**: You can try increasing the Docker client timeout by setting the `DOCKER_CLIENT_TIMEOUT` and `COMPOSE_HTTP_TIMEOUT` environment variables: ```bash export DOCKER_CLIENT_TIMEOUT=300 export COMPOSE_HTTP_TIMEOUT=300 ``` 3. **Check Docker Daemon Logs**: Inspect the Docker daemon logs for more detailed error messages: ```bash sudo journalctl -u docker.service ``` 4. **Update Docker**: Ensure you are using a compatible Docker version. For Dify, Docker 19.03 or later is recommended <sup>[[4]](https://github.com/langgenius/dify-docs/blob/main/en/getting-started/install-self-hosted/docker-compose.md)</sup>. 5. **DNS Issues**: Sometimes DNS resolution issues can cause such errors. You can try changing the DNS server in your Docker daemon configuration (`/etc/docker/daemon.json`): ```json { "dns": ["8.8.8.8", "8.8.4.4"] } ``` Then restart the Docker service: ```bash sudo systemctl restart docker ``` If these steps do not resolve the issue, you might want to look into the detailed environment configuration guide for Dify in a Docker setup <sup>[[5]](https://github.com/langgenius/dify/blob/main/docker/README.md)</sup><sup>[[6]](https://github.com/langgenius/dify/blob/main/docker/.env.example)</sup>. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.*
yindo commented 2026-02-21 18:12:37 -05:00
Author
Owner
Copy Link
Copy Source

@aeeeeeep commented on GitHub (Aug 29, 2025):

replace image: langgenius/ by image: docker.m.daocloud.io/langgenius/ in docker/docker-compose.yaml
it works fine

@aeeeeeep commented on GitHub (Aug 29, 2025): replace `image: langgenius/` by `image: docker.m.daocloud.io/langgenius/` in `docker/docker-compose.yaml` it works fine
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#5792
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?