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

langgenius/dify-api:1.12.0 not found #22003

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

Originally created by @hiratagoh on GitHub (Jan 31, 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.11.4

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

I attempted to update to v1.11.4 following the release notes (https://github.com/langgenius/dify/releases/tag/1.11.4), but I encountered the following error:

$ cd docker
$ docker compose down
$ git checkout main
$ git pull origin main
$ docker compose up -d
[+] up 3/4
 ! Image langgenius/dify-plugin-daemon:0.5.3-local Interrupted              2.3s
 ⠸ Image busybox:latest                            Pulling                  2.3s
 ! Image langgenius/dify-api:1.12.0                Interrupted              2.3s
 ! Image langgenius/dify-web:1.12.0                Interrupted              2.3s
Error response from daemon: manifest for langgenius/dify-api:1.12.0 not found: manifest unknown: manifest unknown

✔️ Expected Behavior

Dify should start up without any errors.

❌ Actual Behavior

The process failed because it attempted to pull container images for v1.12.0, which do not exist yet.

I believe this is because docker-compose.yaml was updated to version 1.12.0 on the main branch in this PR:
chore: update version to 1.12.0 #31726

I was able to resolve the issue by checking out the specific tag instead of using the main branch:

$ git fetch --tags
$ git checkout 1.11.4
$ docker compose up -d

Releasing the v1.12.0 images or reverting the version change in docker-compose.yaml should fix this issue.

Originally created by @hiratagoh on GitHub (Jan 31, 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.11.4 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce I attempted to update to v1.11.4 following the release notes (https://github.com/langgenius/dify/releases/tag/1.11.4), but I encountered the following error: ```bash $ cd docker $ docker compose down $ git checkout main $ git pull origin main $ docker compose up -d [+] up 3/4 ! Image langgenius/dify-plugin-daemon:0.5.3-local Interrupted 2.3s ⠸ Image busybox:latest Pulling 2.3s ! Image langgenius/dify-api:1.12.0 Interrupted 2.3s ! Image langgenius/dify-web:1.12.0 Interrupted 2.3s Error response from daemon: manifest for langgenius/dify-api:1.12.0 not found: manifest unknown: manifest unknown ``` ### ✔️ Expected Behavior Dify should start up without any errors. ### ❌ Actual Behavior The process failed because it attempted to pull container images for `v1.12.0`, which do not exist yet. I believe this is because `docker-compose.yaml` was updated to version 1.12.0 on the `main` branch in this PR: [chore: update version to 1.12.0 #31726](https://github.com/langgenius/dify/pull/31726) I was able to resolve the issue by checking out the specific tag instead of using the main branch: ```bash $ git fetch --tags $ git checkout 1.11.4 $ docker compose up -d ``` Releasing the v1.12.0 images or reverting the version change in `docker-compose.yaml` should fix this issue.
yindo added the 🐞 bug label 2026-02-21 20:15:13 -05:00
yindo closed this issue 2026-02-21 20:15:13 -05:00
yindo commented 2026-02-21 20:15:14 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Jan 31, 2026):

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

The error happens because the main branch's docker-compose.yaml was updated to reference langgenius/dify-api:1.12.0 and related images before those images were published to the Docker registry. This is a normal part of the development workflow—main can reference unreleased versions, which sometimes leads to image pull errors if you deploy directly from main right after a version bump see PR #31726.

Checking out a stable release tag like 1.11.4 is the right workaround, since those tags reference images that are actually available. For production or stable deployments, it's best to use release tags rather than main, unless you specifically want to test unreleased features.

There's currently no official ETA or maintainer comment about when the 1.12.0 images will be published or if the version bump will be reverted. You can either wait for the 1.12.0 images to be released, or continue using the latest stable tag until then. Monitoring the repository for updates is a good idea if you want to switch as soon as the new images are available.

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 (Jan 31, 2026): <!-- Greeting --> Hi @hiratagoh! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the dify team. <!-- Answer --> The error happens because the main branch's `docker-compose.yaml` was updated to reference `langgenius/dify-api:1.12.0` and related images before those images were published to the Docker registry. This is a normal part of the development workflow—main can reference unreleased versions, which sometimes leads to image pull errors if you deploy directly from main right after a version bump [see PR #31726](https://github.com/langgenius/dify/pull/31726). Checking out a stable release tag like `1.11.4` is the right workaround, since those tags reference images that are actually available. For production or stable deployments, it's best to use release tags rather than main, unless you specifically want to test unreleased features. There's currently no official ETA or maintainer comment about when the 1.12.0 images will be published or if the version bump will be reverted. You can either wait for the 1.12.0 images to be released, or continue using the latest stable tag until then. Monitoring the repository for updates is a good idea if you want to switch as soon as the new images are available. <!-- 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/27b9ca7e-d0d4-491a-bdc2-bd64a28be937?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/27b9ca7e-d0d4-491a-bdc2-bd64a28be937?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/27b9ca7e-d0d4-491a-bdc2-bd64a28be937?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/27b9ca7e-d0d4-491a-bdc2-bd64a28be937?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/27b9ca7e-d0d4-491a-bdc2-bd64a28be937?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/27b9ca7e-d0d4-491a-bdc2-bd64a28be937?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/27b9ca7e-d0d4-491a-bdc2-bd64a28be937?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=The%20error%20happens%20because%20the%20main%20branch%27s%20%60docker-compose.yaml%60%20was%20updated%20to%20reference%20%60langgenius/dify-api%3A1.12.0%60%20and%20related%20images%20before%20those%20images%20were%20published%20to%20the%20Docker%20registry.%20This%20is%20a%20normal%20part%20of%20the%20development%20workflow%E2%80%94main%20can%20reference%20unreleased%20versions%2C%20which%20sometimes%20leads%20to%20image%20pull%20errors%20if%20you%20deploy%20directly%20from%20main%20right%20after%20a%20version%20bump%C2%A0%5Bsee%20PR%20%2331726%5D%28https%3A//github.com/langgenius/dify/pull/31726%29.%0A%0AChecking%20out%20a%20stable%20release%20tag%20like%20%601.11.4%60%20is%20the%20right%20workaround%2C%20since%20those%20tags%20reference%20images%20that%20are%20actually%20available.%20For%20production%20or%20stable%20deployments%2C%20it%27s%20best%20to%20use%20release%20tags%20rather%20than%20main%2C%20unless%20you%20specifically%20want%20to%20test%20unreleased%20features.%0A%0AThere%27s%20currently%20no%20official%20ETA%20or%20maintainer%20comment%20about%20when%20the%201.12.0%20images%20will%20be%20published%20or%20if%20the%20version%20bump%20will%20be%20reverted.%20You%20can%20either%20wait%20for%20the%201.12.0%20images%20to%20be%20released%2C%20or%20continue%20using%20the%20latest%20stable%20tag%20until%20then.%20Monitoring%20the%20repository%20for%20updates%20is%20a%20good%20idea%20if%20you%20want%20to%20switch%20as%20soon%20as%20the%20new%20images%20are%20available.)&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/31791)
yindo commented 2026-02-21 20:15:14 -05:00
Author
Owner
Copy Link
Copy Source

@hiratagoh commented on GitHub (Jan 31, 2026):

thanks dosubot.
I’m looking forward to the update to v1.12.0.

@hiratagoh commented on GitHub (Jan 31, 2026): thanks dosubot. I’m looking forward to the update to v1.12.0.
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#22003
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?