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

images download failed #4245

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

Originally created by @Tekkaman-HB on GitHub (Jun 24, 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

error pulling image configuration: download failed after attempts=6: net/http: TLS handshake timeout
image

✔️ Expected Behavior

download 0.6.11 images

❌ Actual Behavior

download failed

Originally created by @Tekkaman-HB on GitHub (Jun 24, 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 error pulling image configuration: download failed after attempts=6: net/http: TLS handshake timeout <img width="1502" alt="image" src="https://github.com/langgenius/dify/assets/48499574/114b332d-13fe-494d-80d5-8623742e72d9"> ### ✔️ Expected Behavior download 0.6.11 images ### ❌ Actual Behavior download failed
yindo added the 🐞 bug label 2026-02-21 18:05:22 -05:00
yindo closed this issue 2026-02-21 18:05:22 -05:00
yindo commented 2026-02-21 18:05:22 -05:00
Author
Owner
Copy Link
Copy Source

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

Hey @Tekkaman-HB, I'm here to help you with any bugs, questions, or contributions you might have for the Dify repository. Let me know how I can assist you!

To resolve the issue of failing to download some images due to a TLS handshake timeout and the warning about an obsolete version in the docker-compose.yaml file when running docker compose pull for Dify version 0.6.11 on a self-hosted Docker setup, follow these steps:

  1. Update Docker Compose Version: Ensure you are using Docker Compose V2, as the documentation suggests using docker compose instead of docker-compose. You can check your Docker Compose version with:

    docker compose version

  2. Update docker-compose.yaml Version: If you receive a warning about an obsolete version in the docker-compose.yaml file, update the version field to a more recent version. For example, change:

    version: '2'

    to:

    version: '3.8'

  3. Handle TLS Handshake Timeout: TLS handshake timeouts can be caused by network issues or Docker Hub rate limits. To mitigate this:

    • Ensure your network connection is stable.
    • Try pulling the images at a different time when the network might be less congested.
    • If you are behind a proxy, ensure your Docker is configured to use the proxy.

  4. Retry the Pull Command: After making the above changes, retry the pull command:

    docker compose pull

  5. Follow Dify's Deployment and Upgrade Instructions: According to the Dify documentation, ensure you follow the correct steps for deployment and upgrading:

    • Clone the Dify source code: 
      git clone https://github.com/langgenius/dify.git
    • Navigate to the Dify docker directory and start the services: 
      cd dify/docker
docker compose up -d
    • For upgrading Dify, follow these steps: 
      cd dify/docker
git pull origin main
docker compose down
docker compose pull
docker compose up -d

  6. Check Deployment Results: After starting the services, ensure all containers are running successfully:

    docker compose ps

By following these steps, you should be able to resolve the issues related to TLS handshake timeouts and the obsolete version warning in your docker-compose.yaml file [1][2][3].

To continue talking to Dosu, mention @dosu.

@dosubot[bot] commented on GitHub (Jun 24, 2024): <!-- Greeting --> Hey @Tekkaman-HB, I'm here to help you with any bugs, questions, or contributions you might have for the Dify repository. Let me know how I can assist you! <!-- Answer --> To resolve the issue of failing to download some images due to a TLS handshake timeout and the warning about an obsolete `version` in the `docker-compose.yaml` file when running `docker compose pull` for Dify version 0.6.11 on a self-hosted Docker setup, follow these steps: 1. **Update Docker Compose Version**: Ensure you are using Docker Compose V2, as the documentation suggests using `docker compose` instead of `docker-compose`. You can check your Docker Compose version with: ```bash docker compose version ``` 2. **Update `docker-compose.yaml` Version**: If you receive a warning about an obsolete `version` in the `docker-compose.yaml` file, update the `version` field to a more recent version. For example, change: ```yaml version: '2' ``` to: ```yaml version: '3.8' ``` 3. **Handle TLS Handshake Timeout**: TLS handshake timeouts can be caused by network issues or Docker Hub rate limits. To mitigate this: - Ensure your network connection is stable. - Try pulling the images at a different time when the network might be less congested. - If you are behind a proxy, ensure your Docker is configured to use the proxy. 4. **Retry the Pull Command**: After making the above changes, retry the pull command: ```bash docker compose pull ``` 5. **Follow Dify's Deployment and Upgrade Instructions**: According to the Dify documentation, ensure you follow the correct steps for deployment and upgrading: - Clone the Dify source code: ```bash git clone https://github.com/langgenius/dify.git ``` - Navigate to the Dify docker directory and start the services: ```bash cd dify/docker docker compose up -d ``` - For upgrading Dify, follow these steps: ```bash cd dify/docker git pull origin main docker compose down docker compose pull docker compose up -d ``` 6. **Check Deployment Results**: After starting the services, ensure all containers are running successfully: ```bash docker compose ps ``` By following these steps, you should be able to resolve the issues related to TLS handshake timeouts and the obsolete `version` warning in your `docker-compose.yaml` file <sup>[[1]](https://github.com/langgenius/dify-docs/blob/main/jp/getting-started/install-self-hosted/docker-compose.md)</sup><sup>[[2]](https://github.com/langgenius/dify-docs/blob/main/zh_CN/getting-started/install-self-hosted/docker-compose.md)</sup><sup>[[3]](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:22 -05:00
Author
Owner
Copy Link
Copy Source

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

This is a general network issue.

@crazywoola commented on GitHub (Jun 24, 2024): This is a general network issue.
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#4245
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?