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

Unstructure service is not being pulled due to wrong image address #5528

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

Originally created by @taowang1993 on GitHub (Sep 10, 2024).

Originally assigned to: @laipz8200 on GitHub.

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.0

Cloud or Self Hosted

Self Hosted (Docker), Self Hosted (Source)

Steps to reproduce

should be downloads.unstructured.io/unstructured-io/unstructured:latest

should not be downloads.unstructured.io/unstructured-io/unstructured-api:latest

official docs: https://docs.unstructured.io/open-source/installation/docker-installation

✔️ Expected Behavior

No response

❌ Actual Behavior

No response

Originally created by @taowang1993 on GitHub (Sep 10, 2024). Originally assigned to: @laipz8200 on GitHub. ### 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.0 ### Cloud or Self Hosted Self Hosted (Docker), Self Hosted (Source) ### Steps to reproduce should be downloads.unstructured.io/unstructured-io/unstructured:latest should not be downloads.unstructured.io/unstructured-io/unstructured-api:latest official docs: https://docs.unstructured.io/open-source/installation/docker-installation ### ✔️ Expected Behavior _No response_ ### ❌ Actual Behavior _No response_
yindo added the 🐞 bug🤔 cant-reproduce labels 2026-02-21 18:11:28 -05:00
yindo closed this issue 2026-02-21 18:11:28 -05:00
yindo commented 2026-02-21 18:11:28 -05:00
Author
Owner
Copy Link
Copy Source

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

I found a similar closed issue where the Unstructure service was not being pulled due to the wrong image address. The solution involves setting the UNSTRUCTURED_API_URL environment variable correctly.

To resolve this, you need to configure the UNSTRUCTURED_API_URL with the correct API path for the Unstructured service. For example:

UNSTRUCTURED_API_URL=http://unstructured:8000/general/v0/general

Make sure this URL points to the correct address where the Unstructured service is hosted [1].

Additionally, the correct image address for the Unstructured service in the Dify documentation is:

http://unstructured:8000/general/v0/general

This address is specified under the UNSTRUCTURED_API_URL configuration when the ETL_TYPE is set to Unstructured [2][3].

In the docker-compose.yml file, the Unstructured service should be configured as follows:

unstructured:
  image: downloads.unstructured.io/unstructured-io/unstructured-api:latest
  profiles:
    - unstructured
  restart: always
  volumes:
    - ./volumes/unstructured:/app/data

Ensure that the ETL_TYPE environment variable is set to Unstructured in the .env file for the API and worker services:

ETL_TYPE=Unstructured
UNSTRUCTURED_API_URL=http://unstructured:8000/general/v0/general

By following these steps, you should be able to resolve the issue with the Unstructured service not being pulled due to the wrong image address [4][1][5].

To continue talking to Dosu, mention @dosu.

@dosubot[bot] commented on GitHub (Sep 10, 2024): <!-- Answer --> I found a similar closed issue where the Unstructure service was not being pulled due to the wrong image address. The solution involves setting the `UNSTRUCTURED_API_URL` environment variable correctly. To resolve this, you need to configure the `UNSTRUCTURED_API_URL` with the correct API path for the Unstructured service. For example: ```env UNSTRUCTURED_API_URL=http://unstructured:8000/general/v0/general ``` Make sure this URL points to the correct address where the Unstructured service is hosted <sup>[[1]](https://github.com/langgenius/dify/blob/main/docker/.env.example)</sup>. Additionally, the correct image address for the Unstructured service in the Dify documentation is: ```plaintext http://unstructured:8000/general/v0/general ``` This address is specified under the `UNSTRUCTURED_API_URL` configuration when the `ETL_TYPE` is set to `Unstructured` <sup>[[2]](https://github.com/langgenius/dify-docs/blob/main/en/getting-started/install-self-hosted/environments.md)</sup><sup>[[3]](https://github.com/langgenius/dify-docs/blob/main/zh_CN/getting-started/install-self-hosted/environments.md)</sup>. In the `docker-compose.yml` file, the Unstructured service should be configured as follows: ```yaml unstructured: image: downloads.unstructured.io/unstructured-io/unstructured-api:latest profiles: - unstructured restart: always volumes: - ./volumes/unstructured:/app/data ``` Ensure that the `ETL_TYPE` environment variable is set to `Unstructured` in the `.env` file for the API and worker services: ```env ETL_TYPE=Unstructured UNSTRUCTURED_API_URL=http://unstructured:8000/general/v0/general ``` By following these steps, you should be able to resolve the issue with the Unstructured service not being pulled due to the wrong image address <sup>[[4]](https://github.com/langgenius/dify/blob/main/docker/docker-compose.yaml)</sup><sup>[[1]](https://github.com/langgenius/dify/blob/main/docker/.env.example)</sup><sup>[[5]](https://github.com/langgenius/dify/blob/main/docker/README.md)</sup>. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.*
yindo commented 2026-02-21 18:11:28 -05:00
Author
Owner
Copy Link
Copy Source

@taowang1993 commented on GitHub (Sep 10, 2024):

The image has been changed to unstructured downloads.unstructured.io/unstructured-io/unstructured:latest

without -api

please read the docs

and i already set the variables to
ETL_TYPE=Unstructured
UNSTRUCTURED_API_URL=http://unstructured:8000/general/v0/general

it is still not pulling the image

@taowang1993 commented on GitHub (Sep 10, 2024): The image has been changed to unstructured downloads.unstructured.io/unstructured-io/unstructured:latest without -api please read the docs and i already set the variables to ETL_TYPE=Unstructured UNSTRUCTURED_API_URL=http://unstructured:8000/general/v0/general it is still not pulling the image
yindo commented 2026-02-21 18:11:28 -05:00
Author
Owner
Copy Link
Copy Source

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

The issue might be due to the incorrect image name specified in the docker-compose.yaml file. The correct image name should be downloads.unstructured.io/unstructured-io/unstructured-api:latest instead of downloads.unstructured.io/unstructured-io/unstructured:latest.

Here is the relevant section of the docker-compose.yaml file with the corrected image name:

unstructured:
  image: downloads.unstructured.io/unstructured-io/unstructured-api:latest
  profiles:
    - unstructured
  restart: always
  volumes:
    - ./volumes/unstructured:/app/data

Make sure to update the image name in your docker-compose.yaml file and then restart the service [1].

To continue talking to Dosu, mention @dosu.

@dosubot[bot] commented on GitHub (Sep 10, 2024): <!-- Answer --> The issue might be due to the incorrect image name specified in the `docker-compose.yaml` file. The correct image name should be `downloads.unstructured.io/unstructured-io/unstructured-api:latest` instead of `downloads.unstructured.io/unstructured-io/unstructured:latest`. Here is the relevant section of the `docker-compose.yaml` file with the corrected image name: ```yaml unstructured: image: downloads.unstructured.io/unstructured-io/unstructured-api:latest profiles: - unstructured restart: always volumes: - ./volumes/unstructured:/app/data ``` Make sure to update the image name in your `docker-compose.yaml` file and then restart the service <sup>[[1]](https://github.com/langgenius/dify/blob/main/docker/docker-compose.yaml)</sup>. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.*
yindo commented 2026-02-21 18:11:28 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Sep 10, 2024):

You can change the url in docker-compose.yml to see if this works and you can open a pr for this as well.

I pulled this image but it seems works for me.

@crazywoola commented on GitHub (Sep 10, 2024): ~You can change the url in docker-compose.yml to see if this works and you can open a pr for this as well.~ I pulled this image but it seems works for me.
yindo commented 2026-02-21 18:11:28 -05:00
Author
Owner
Copy Link
Copy Source

@taowang1993 commented on GitHub (Sep 11, 2024):

I have to use this command, right? If so, please add notes in the docs. Thanks~
docker-compose --profile unstructured up

@taowang1993 commented on GitHub (Sep 11, 2024): I have to use this command, right? If so, please add notes in the docs. Thanks~ docker-compose --profile unstructured up
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 🤔 cant-reproduce
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#5528
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?