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

manifest for langgenius/dify-web:0.15.1 not found: manifest unknown: manifest unknown #7701

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

Originally created by @infinitnet on GitHub (Jan 13, 2025).

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

15.1

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Updating from 15 to 15.1 (Docker) results in manifest for langgenius/dify-web:0.15.1 not found: manifest unknown: manifest unknown on docker compose up -d

✔️ Expected Behavior

Docker containers should start

❌ Actual Behavior

docker compose up -d fails with manifest for langgenius/dify-web:0.15.1 not found: manifest unknown: manifest unknown

Originally created by @infinitnet on GitHub (Jan 13, 2025). 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 15.1 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce Updating from 15 to 15.1 (Docker) results in `manifest for langgenius/dify-web:0.15.1 not found: manifest unknown: manifest unknown` on `docker compose up -d` ### ✔️ Expected Behavior Docker containers should start ### ❌ Actual Behavior `docker compose up -d` fails with `manifest for langgenius/dify-web:0.15.1 not found: manifest unknown: manifest unknown`
yindo added the 🐞 bug label 2026-02-21 18:21:56 -05:00
yindo closed this issue 2026-02-21 18:21:56 -05:00
yindo commented 2026-02-21 18:21:57 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Jan 13, 2025):

I found a similar open issue where the Docker manifest for a specific version was not found. The suggested solution is to build the Docker image yourself if it is not available on DockerHub. Here are the steps you can follow to build the langgenius/dify-web Docker image locally:

  1. Clone the Dify repository:

    git clone https://github.com/langgenius/dify.git

  2. Navigate to the Dify directory:

    cd dify

  3. Build the Docker image with the 0.15.1 tag:

    docker build -t langgenius/dify-web:0.15.1 .

After building the image, you should be able to proceed with docker compose up -d without encountering the manifest error [1][2].

To continue talking to Dosu, mention @dosu.

Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other

@dosubot[bot] commented on GitHub (Jan 13, 2025): <!-- Answer --> I found a similar open issue where the Docker manifest for a specific version was not found. The suggested solution is to build the Docker image yourself if it is not available on DockerHub. Here are the steps you can follow to build the `langgenius/dify-web` Docker image locally: 1. **Clone the Dify repository:** ```bash git clone https://github.com/langgenius/dify.git ``` 2. **Navigate to the Dify directory:** ```bash cd dify ``` 3. **Build the Docker image with the `0.15.1` tag:** ```bash docker build -t langgenius/dify-web:0.15.1 . ``` After building the image, you should be able to proceed with `docker compose up -d` without encountering the manifest error <sup>[[1]](https://github.com/langgenius/dify/issues/3379)</sup><sup>[[2]](https://github.com/langgenius/dify/issues/8203)</sup>. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.* --- <sup>Help Dosu learn! Give it feedback: [Great Response](https://app.dosu.dev/response-feedback/82712fee-051e-412d-852a-589c3f9a49a1?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/82712fee-051e-412d-852a-589c3f9a49a1?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/82712fee-051e-412d-852a-589c3f9a49a1?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/82712fee-051e-412d-852a-589c3f9a49a1?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/82712fee-051e-412d-852a-589c3f9a49a1?feedback_type=hallucination) | [Other](https://app.dosu.dev/response-feedback/82712fee-051e-412d-852a-589c3f9a49a1?feedback_type=other)</sup>
yindo commented 2026-02-21 18:21:57 -05:00
Author
Owner
Copy Link
Copy Source

@leoleelxh commented on GitHub (Jan 13, 2025):

the same issue！when build the docker image，show：
root@docker:~/dify/dify# docker build -t langgenius/dify-web:0.15.1 .
[+] Building 0.2s (1/1) FINISHED docker:default
=> [internal] load build definition from Dockerfile 0.0s
=> => transferring dockerfile: 2B 0.0s
ERROR: failed to solve: failed to read dockerfile: open Dockerfile: no such file or directory

@leoleelxh commented on GitHub (Jan 13, 2025): the same issue！when build the docker image，show： root@docker:~/dify/dify# docker build -t langgenius/dify-web:0.15.1 . [+] Building 0.2s (1/1) FINISHED docker:default => [internal] load build definition from Dockerfile 0.0s => => transferring dockerfile: 2B 0.0s ERROR: failed to solve: failed to read dockerfile: open Dockerfile: no such file or directory
yindo commented 2026-02-21 18:21:57 -05:00
Author
Owner
Copy Link
Copy Source

@infinitnet commented on GitHub (Jan 13, 2025):

the same issue！when build the docker image，show： root@docker:~/dify/dify# docker build -t langgenius/dify-web:0.15.1 . [+] Building 0.2s (1/1) FINISHED docker:default => [internal] load build definition from Dockerfile 0.0s => => transferring dockerfile: 2B 0.0s ERROR: failed to solve: failed to read dockerfile: open Dockerfile: no such file or directory

Works now - seems to have been because of a delay between the release tag and publishing the manifests on DockerHub. Dify team should adjust the release workflow accordingly to get the manifests ready before publishing the release. Leaving this issue open because of this as it's not been the first ticket about this problem.

@infinitnet commented on GitHub (Jan 13, 2025): > the same issue！when build the docker image，show： root@docker:~/dify/dify# docker build -t langgenius/dify-web:0.15.1 . [+] Building 0.2s (1/1) FINISHED docker:default => [internal] load build definition from Dockerfile 0.0s => => transferring dockerfile: 2B 0.0s ERROR: failed to solve: failed to read dockerfile: open Dockerfile: no such file or directory Works now - seems to have been because of a delay between the release tag and publishing the manifests on DockerHub. Dify team should adjust the release workflow accordingly to get the manifests ready before publishing the release. Leaving this issue open because of this as it's not been the first ticket about this problem.
yindo commented 2026-02-21 18:21:57 -05:00
Author
Owner
Copy Link
Copy Source

@laipz8200 commented on GitHub (Jan 13, 2025):

Thank you for your interest! You can check the build progress at https://github.com/langgenius/dify/actions/runs/12746143020, and it's available now. Building the image before release is another topic, so if you need assistance with that, feel free to open a new issue.

@laipz8200 commented on GitHub (Jan 13, 2025): Thank you for your interest! You can check the build progress at https://github.com/langgenius/dify/actions/runs/12746143020, and it's available now. Building the image before release is another topic, so if you need assistance with that, feel free to open a new issue.
yindo commented 2026-02-21 18:21:57 -05:00
Author
Owner
Copy Link
Copy Source

@songzijiang commented on GitHub (Feb 17, 2025):

the same issue！when build the docker image，show： root@docker:~/dify/dify# docker build -t langgenius/dify-web:0.15.1 . [+] Building 0.2s (1/1) FINISHED docker:default => [internal] load build definition from Dockerfile 0.0s => => transferring dockerfile: 2B 0.0s ERROR: failed to solve: failed to read dockerfile: open Dockerfile: no such file or directory

I have the same problems? How could I solve this problems?

@songzijiang commented on GitHub (Feb 17, 2025): > the same issue！when build the docker image，show： root@docker:~/dify/dify# docker build -t langgenius/dify-web:0.15.1 . [+] Building 0.2s (1/1) FINISHED docker:default => [internal] load build definition from Dockerfile 0.0s => => transferring dockerfile: 2B 0.0s ERROR: failed to solve: failed to read dockerfile: open Dockerfile: no such file or directory I have the same problems? How could I solve this problems?
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#7701
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?