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

0.6.11升级失败，镜像拉取超时问题 #4212

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

Originally created by @dming519 on GitHub (Jun 21, 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).
  • Please do not modify this template :) and fill in all the required fields.

Dify version

0.6.11

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

超时了，尝试了几种方法都没解决，求救一下大神。
bug1
bug2
bug3

✔️ Expected Behavior

No response

❌ Actual Behavior

No response

Originally created by @dming519 on GitHub (Jun 21, 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] Please do not modify this template :) and fill in all the required fields. ### Dify version 0.6.11 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce 超时了，尝试了几种方法都没解决，求救一下大神。 ![bug1](https://github.com/langgenius/dify/assets/28173211/91f30ac1-4f61-413d-b895-1b90fdfa71ca) ![bug2](https://github.com/langgenius/dify/assets/28173211/d706555c-e673-41ae-91d9-50c1f3ce8f19) ![bug3](https://github.com/langgenius/dify/assets/28173211/129c19e0-94d6-44c1-9da0-361d31d57a13) ### ✔️ Expected Behavior _No response_ ### ❌ Actual Behavior _No response_
yindo added the 🐞 bug label 2026-02-21 18:05:13 -05:00
yindo closed this issue 2026-02-21 18:05:13 -05:00
yindo commented 2026-02-21 18:05:14 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Jun 21, 2024):

@dming519 你好！我是Dosu，一个可以帮助你解决 bug、回答问题并成为贡献者的机器人。我会在等待人类维护者的过程中帮助你。

To resolve the timeout issue when pulling Docker images during the upgrade to version 0.6.11 of Dify in a self-hosted Docker environment, you can follow these steps:

  1. Navigate to the Dify Docker directory:

    cd dify/docker

  2. Pull the latest changes from the repository:

    git pull origin main

  3. Stop the running containers:

    docker compose down

  4. Increase the Docker client timeout:
    Set the COMPOSE_HTTP_TIMEOUT environment variable to a higher value (e.g., 200 seconds) to avoid timeout issues.

    export COMPOSE_HTTP_TIMEOUT=200

  5. Pull the latest Docker images:

    docker compose pull

  6. Start the containers:

    docker compose up -d

By increasing the COMPOSE_HTTP_TIMEOUT, you give Docker more time to pull the images, which can help prevent timeout issues.

Additionally, ensure that your Docker environment meets the prerequisites for running Dify, such as having Docker 19.03 or later and Docker Compose 1.25.1 or later [1][2].

To continue talking to Dosu, mention @dosu.

@dosubot[bot] commented on GitHub (Jun 21, 2024): <!-- Greeting --> @dming519 你好！我是[Dosu](https://dosu.dev)，一个可以帮助你解决 bug、回答问题并成为贡献者的机器人。我会在等待人类维护者的过程中帮助你。 <!-- Answer --> To resolve the timeout issue when pulling Docker images during the upgrade to version 0.6.11 of Dify in a self-hosted Docker environment, you can follow these steps: 1. **Navigate to the Dify Docker directory:** ```bash cd dify/docker ``` 2. **Pull the latest changes from the repository:** ```bash git pull origin main ``` 3. **Stop the running containers:** ```bash docker compose down ``` 4. **Increase the Docker client timeout:** Set the `COMPOSE_HTTP_TIMEOUT` environment variable to a higher value (e.g., 200 seconds) to avoid timeout issues. ```bash export COMPOSE_HTTP_TIMEOUT=200 ``` 5. **Pull the latest Docker images:** ```bash docker compose pull ``` 6. **Start the containers:** ```bash docker compose up -d ``` By increasing the `COMPOSE_HTTP_TIMEOUT`, you give Docker more time to pull the images, which can help prevent timeout issues. Additionally, ensure that your Docker environment meets the prerequisites for running Dify, such as having Docker 19.03 or later and Docker Compose 1.25.1 or later <sup>[[1]](https://github.com/langgenius/dify-docs/blob/main/zh_CN/getting-started/install-self-hosted/docker-compose.md)</sup><sup>[[2]](https://github.com/langgenius/dify-docs/blob/main/en/getting-started/install-self-hosted/docker-compose.md)</sup>. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.*
yindo commented 2026-02-21 18:05:14 -05:00
Author
Owner
Copy Link
Copy Source

@hxgqh commented on GitHub (Jun 23, 2024):

貌似是最近国内的所有docker镜像集体停了？能否加一个国内源的docker-compose.yml？

@hxgqh commented on GitHub (Jun 23, 2024): 貌似是最近国内的所有docker镜像集体停了？能否加一个国内源的docker-compose.yml？
yindo commented 2026-02-21 18:05:14 -05:00
Author
Owner
Copy Link
Copy Source

@dming519 commented on GitHub (Jun 23, 2024):

我根据上面的解决方案进行设置：export COMPOSE_HTTP_TIMEOUT=200，把超时时间设置到2000，最后还是i/o timeout问题。如果有成功解决的朋友麻烦分享一下解决的方案，非常感谢。

@dming519 commented on GitHub (Jun 23, 2024): 我根据上面的解决方案进行设置：export COMPOSE_HTTP_TIMEOUT=200，把超时时间设置到2000，最后还是i/o timeout问题。如果有成功解决的朋友麻烦分享一下解决的方案，非常感谢。
yindo commented 2026-02-21 18:05:14 -05:00
Author
Owner
Copy Link
Copy Source

@nickboyabc commented on GitHub (Jun 24, 2024):

关注中，好像要改配置文件？

@nickboyabc commented on GitHub (Jun 24, 2024): 关注中，好像要改配置文件？
yindo commented 2026-02-21 18:05:14 -05:00
Author
Owner
Copy Link
Copy Source

@xinzhics commented on GitHub (Jun 24, 2024):

我也是，更改了阿里云的镜像地址也不管用，不知道这个镜像是否仅在docker hub上，国内这个网，太头疼了

@xinzhics commented on GitHub (Jun 24, 2024): 我也是，更改了阿里云的镜像地址也不管用，不知道这个镜像是否仅在docker hub上，国内这个网，太头疼了
yindo commented 2026-02-21 18:05:14 -05:00
Author
Owner
Copy Link
Copy Source

@ycdhqzhiai commented on GitHub (Jul 8, 2024):

有解决的吗

@ycdhqzhiai commented on GitHub (Jul 8, 2024): 有解决的吗
yindo commented 2026-02-21 18:05:14 -05:00
Author
Owner
Copy Link
Copy Source

@dming519 commented on GitHub (Jul 8, 2024):

看这个https://github.com/imashen/docker-aio
配置docker的加速源

@dming519 commented on GitHub (Jul 8, 2024): 看这个https://github.com/imashen/docker-aio 配置docker的加速源
yindo commented 2026-02-21 18:05:14 -05:00
Author
Owner
Copy Link
Copy Source

@lichunnan commented on GitHub (Aug 1, 2024):

看这个https://github.com/imashen/docker-aio 配置docker的加速源

刚测试过了，这个方法好用！感谢

@lichunnan commented on GitHub (Aug 1, 2024): > 看这个https://github.com/imashen/docker-aio 配置docker的加速源 刚测试过了，这个方法好用！感谢
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#4212
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?