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

Get "https://registry-1.docker.io/v2/": context deadline exceeded #12561

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

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

Image

✔️ Expected Behavior

No response

❌ Actual Behavior

No response

Originally created by @mxyd on GitHub (Apr 5, 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 ![Image](https://github.com/user-attachments/assets/1021890c-bf39-42a9-99b5-426c27593084) ### ✔️ Expected Behavior _No response_ ### ❌ Actual Behavior _No response_
yindo closed this issue 2026-02-21 19:08:00 -05:00
yindo commented 2026-02-21 19:08:00 -05:00
Author
Owner
Copy Link
Copy Source

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

I found a similar issue that was resolved. The problem seems to be related to network configuration or firewall settings blocking the connection to Docker Hub. Here are some 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.

  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

These steps were suggested in a similar discussion [1].

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 5, 2025): <!-- Answer --> I found a similar issue that was resolved. The problem seems to be related to network configuration or firewall settings blocking the connection to Docker Hub. Here are some 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. 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 ``` These steps were suggested in a similar discussion <sup>[[1]](https://github.com/langgenius/dify/discussions/14765)</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/f5f7924f-0835-4018-ba0d-2b3e36ae7863?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/f5f7924f-0835-4018-ba0d-2b3e36ae7863?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/f5f7924f-0835-4018-ba0d-2b3e36ae7863?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/f5f7924f-0835-4018-ba0d-2b3e36ae7863?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/f5f7924f-0835-4018-ba0d-2b3e36ae7863?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/f5f7924f-0835-4018-ba0d-2b3e36ae7863?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/f5f7924f-0835-4018-ba0d-2b3e36ae7863?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
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#12561
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?