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

Docker compse file try to pull not exists dify-api / dify-web image #22007

New Issue
Closed
opened 2026-02-21 20:15:14 -05:00 by yindo · 4 comments
yindo commented 2026-02-21 20:15:14 -05:00
Owner
Copy Link
Copy Source

Originally created by @liusmycroft on GitHub (Feb 1, 2026).

Self Checks

  • I have read the Contributing Guide and Language Policy.
  • 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, otherwise it will be closed.
  • 【中文用户 & Non English User】请使用英语提交，否则会被关闭 ：）
  • Please do not modify this template :) and fill in all the required fields.

Dify version

1.12.0

Cloud or Self Hosted

Self Hosted (Source)

Steps to reproduce

git clone https://github.com/langgenius/dify.git
cd docker
docker compose up -d

docker will try to pull not exists image, dify-api 1.12.0 and dify-web 1.12.0 image not exists in docker-hub

✔️ Expected Behavior

dify-api 1.12.0 and dify-web 1.12.0 image exists

❌ Actual Behavior

No response

Originally created by @liusmycroft on GitHub (Feb 1, 2026). ### Self Checks - [x] I have read the [Contributing Guide](https://github.com/langgenius/dify/blob/main/CONTRIBUTING.md) and [Language Policy](https://github.com/langgenius/dify/issues/1542). - [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, otherwise it will be closed. - [x] 【中文用户 & Non English User】请使用英语提交，否则会被关闭 ：） - [x] Please do not modify this template :) and fill in all the required fields. ### Dify version 1.12.0 ### Cloud or Self Hosted Self Hosted (Source) ### Steps to reproduce git clone https://github.com/langgenius/dify.git cd docker docker compose up -d docker will try to pull not exists image, dify-api 1.12.0 and dify-web 1.12.0 image not exists in docker-hub ### ✔️ Expected Behavior dify-api 1.12.0 and dify-web 1.12.0 image exists ### ❌ Actual Behavior _No response_
yindo added the 🐞 bug label 2026-02-21 20:15:14 -05:00
yindo closed this issue 2026-02-21 20:15:14 -05:00
yindo commented 2026-02-21 20:15:14 -05:00
Author
Owner
Copy Link
Copy Source

@liusmycroft commented on GitHub (Feb 1, 2026):

I try to change dify-api and dify-web tag from 1.12.0 to 1.11.0, and it works. But if I change the tag to 'main', when I visit localhost, it will stuck into loading pages

@liusmycroft commented on GitHub (Feb 1, 2026): I try to change dify-api and dify-web tag from 1.12.0 to 1.11.0, and it works. But if I change the tag to 'main', when I visit localhost, it will stuck into loading pages
yindo commented 2026-02-21 20:15:15 -05:00
Author
Owner
Copy Link
Copy Source

@liusmycroft commented on GitHub (Feb 1, 2026):

Image
@liusmycroft commented on GitHub (Feb 1, 2026): <img width="1589" height="701" alt="Image" src="https://github.com/user-attachments/assets/5a59916d-f33b-4c00-9331-85847abb01d5" />
yindo commented 2026-02-21 20:15:15 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Feb 1, 2026):

Hi @liusmycroft! I'm Dosu and I’m helping the dify team.

You're right—there are no '1.12.0' tags for dify-web (or dify-api) on Docker Hub, which is why Docker Compose can't pull those images for v1.12.0 deployments. This happened because the main branch was updated to reference the new version before the images were published, which is normal in open-source workflows but causes pull errors if you deploy right after a version bump see explanation.

For now, the recommended workaround is to use a stable release tag like 1.11.4, which points to images that do exist on Docker Hub. If you need features from 1.12.0 before the images are published, you can build the images locally using the Dockerfiles in the repo (api/Dockerfile and web/Dockerfile), then tag them as 1.12.0 so Compose will use your local builds.

To build and tag locally:

# From the root of the repo
docker build -t langgenius/dify-api:1.12.0 -f api/Dockerfile ./api
docker build -t langgenius/dify-web:1.12.0 -f web/Dockerfile ./web

Then run docker compose up -d as usual.

If you want to switch back to official images later, just update your compose file to the new tag once it's published. For production, stick to stable release tags unless you specifically want to test unreleased features details.

Let me know if you need step-by-step help with the local build process!

To reply, just mention @dosu.

How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other

Chat with Dosu Open in Cursor Join Discord Share on X

@dosubot[bot] commented on GitHub (Feb 1, 2026): <!-- Greeting --> Hi @liusmycroft! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the dify team. <!-- Answer --> You're right—there are no '1.12.0' tags for `dify-web` (or `dify-api`) on Docker Hub, which is why Docker Compose can't pull those images for v1.12.0 deployments. This happened because the main branch was updated to reference the new version before the images were published, which is normal in open-source workflows but causes pull errors if you deploy right after a version bump [see explanation](https://github.com/langgenius/dify/issues/31791). For now, the recommended workaround is to use a stable release tag like `1.11.4`, which points to images that do exist on Docker Hub. If you need features from 1.12.0 before the images are published, you can build the images locally using the Dockerfiles in the repo (`api/Dockerfile` and `web/Dockerfile`), then tag them as `1.12.0` so Compose will use your local builds. To build and tag locally: ```bash # From the root of the repo docker build -t langgenius/dify-api:1.12.0 -f api/Dockerfile ./api docker build -t langgenius/dify-web:1.12.0 -f web/Dockerfile ./web ``` Then run `docker compose up -d` as usual. If you want to switch back to official images later, just update your compose file to the new tag once it's published. For production, stick to stable release tags unless you specifically want to test unreleased features [details](https://github.com/langgenius/dify/issues/31791). Let me know if you need step-by-step help with the local build process! <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/0c2d305d-54f5-4191-9739-17a50decf877?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/0c2d305d-54f5-4191-9739-17a50decf877?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/0c2d305d-54f5-4191-9739-17a50decf877?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/0c2d305d-54f5-4191-9739-17a50decf877?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/0c2d305d-54f5-4191-9739-17a50decf877?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/0c2d305d-54f5-4191-9739-17a50decf877?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/0c2d305d-54f5-4191-9739-17a50decf877?feedback_type=other)</sup> [![Chat with Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/6088a4f4-073a-43f3-b3d4-4f06fb0c05a0/ask?utm_source=github)&nbsp;[![Open in Cursor](https://dosu.dev/dosu-in-cursor.svg)](https://cursor.com/link/prompt?text=You%27re%20right%E2%80%94there%20are%20no%20%271.12.0%27%20tags%20for%20%60dify-web%60%20%28or%20%60dify-api%60%29%20on%20Docker%20Hub%2C%20which%20is%20why%20Docker%20Compose%20can%27t%20pull%20those%20images%20for%20v1.12.0%20deployments.%20This%20happened%20because%20the%20main%20branch%20was%20updated%20to%20reference%20the%20new%20version%20before%20the%20images%20were%20published%2C%20which%20is%20normal%20in%20open-source%20workflows%20but%20causes%20pull%20errors%20if%20you%20deploy%20right%20after%20a%20version%20bump%C2%A0%5Bsee%20explanation%5D%28https%3A//github.com/langgenius/dify/issues/31791%29.%0A%0AFor%20now%2C%20the%20recommended%20workaround%20is%20to%20use%20a%20stable%20release%20tag%20like%20%601.11.4%60%2C%20which%20points%20to%20images%20that%20do%20exist%20on%20Docker%20Hub.%20If%20you%20need%20features%20from%201.12.0%20before%20the%20images%20are%20published%2C%20you%20can%20build%20the%20images%20locally%20using%20the%20Dockerfiles%20in%20the%20repo%20%28%60api/Dockerfile%60%20and%20%60web/Dockerfile%60%29%2C%20then%20tag%20them%20as%20%601.12.0%60%20so%20Compose%20will%20use%20your%20local%20builds.%0A%0ATo%20build%20and%20tag%20locally%3A%0A%60%60%60bash%0A%23%20From%20the%20root%20of%20the%20repo%0Adocker%20build%20-t%20langgenius/dify-api%3A1.12.0%20-f%20api/Dockerfile%20./api%0Adocker%20build%20-t%20langgenius/dify-web%3A1.12.0%20-f%20web/Dockerfile%20./web%0A%60%60%60%0AThen%20run%20%60docker%20compose%20up%20-d%60%20as%20usual.%0A%0AIf%20you%20want%20to%20switch%20back%20to%20official%20images%20later%2C%20just%20update%20your%20compose%20file%20to%20the%20new%20tag%20once%20it%27s%20published.%20For%20production%2C%20stick%20to%20stable%20release%20tags%20unless%20you%20specifically%20want%20to%20test%20unreleased%20features%C2%A0%5Bdetails%5D%28https%3A//github.com/langgenius/dify/issues/31791%29.%0A%0ALet%20me%20know%20if%20you%20need%20step-by-step%20help%20with%20the%20local%20build%20process%21)&nbsp;[![Join Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot)&nbsp;[![Share on X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/langgenius/dify/issues/31798)
yindo commented 2026-02-21 20:15:15 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Feb 1, 2026):

Haven't released this version yet.

@crazywoola commented on GitHub (Feb 1, 2026): Haven't released this version yet.
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#22007
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?