Error response from daemon: manifest for langgenius/dify-api:0.8.0 not found: manifest unknown: manifest unknown #5512

Closed
opened 2026-02-21 18:11:22 -05:00 by yindo · 3 comments
Owner

Originally created by @warlock8238 on GitHub (Sep 10, 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).
  • [FOR CHINESE USERS] 请务必使用英文提交 Issue,否则会被关闭。谢谢!:)
  • Please do not modify this template :) and fill in all the required fields.

Dify version

langgenius/dify-web:0.8.0

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

root@VM-8-31-ubuntu:/home/ubuntu/dify/dify/docker# docker compose pull
WARN[0000] The "CERTBOT_EMAIL" variable is not set. Defaulting to a blank string.
WARN[0000] The "CERTBOT_DOMAIN" variable is not set. Defaulting to a blank string.
[+] Pulling 9/9
✔ worker Skipped - Image is already being pulled by api 0.0s
✔ weaviate Pulled 2.0s
✔ nginx Pulled 2.0s
✘ web Error 2.6s
✔ sandbox Pulled 2.0s
✘ api Error 2.6s
✔ db Pulled 1.9s
✔ redis Pulled 1.9s
✔ ssrf_proxy Pulled 2.0s
Error response from daemon: manifest for langgenius/dify-api:0.8.0 not found: manifest unknown: manifest unknown

✔️ Expected Behavior

All Images pulled

Actual Behaviors is

Error response from daemon: manifest for langgenius/dify-api:0.8.0 not found: manifest unknown: manifest unknown

Originally created by @warlock8238 on GitHub (Sep 10, 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] [FOR CHINESE USERS] 请务必使用英文提交 Issue,否则会被关闭。谢谢!:) - [X] Please do not modify this template :) and fill in all the required fields. ### Dify version langgenius/dify-web:0.8.0 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce root@VM-8-31-ubuntu:/home/ubuntu/dify/dify/docker# docker compose pull WARN[0000] The "CERTBOT_EMAIL" variable is not set. Defaulting to a blank string. WARN[0000] The "CERTBOT_DOMAIN" variable is not set. Defaulting to a blank string. [+] Pulling 9/9 ✔ worker Skipped - Image is already being pulled by api 0.0s ✔ weaviate Pulled 2.0s ✔ nginx Pulled 2.0s ✘ web Error 2.6s ✔ sandbox Pulled 2.0s ✘ api Error 2.6s ✔ db Pulled 1.9s ✔ redis Pulled 1.9s ✔ ssrf_proxy Pulled 2.0s Error response from daemon: manifest for langgenius/dify-api:0.8.0 not found: manifest unknown: manifest unknown ### ✔️ Expected Behavior All Images pulled ### ❌ Actual Behaviors is Error response from daemon: manifest for langgenius/dify-api:0.8.0 not found: manifest unknown: manifest unknown
yindo closed this issue 2026-02-21 18:11:22 -05:00
Author
Owner

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

Hi @warlock8238! I'm here to help you with any bugs, questions, or contributions you have for langgenius/dify. Let's figure out the issue you're facing together.

I found a similar 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 to build the langgenius/dify-api Docker image from the source code:

  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:

    docker build -t langgenius/dify-api:0.8.0 -f api/Dockerfile .
    

This will build the langgenius/dify-api:0.8.0 image locally, and you should be able to proceed with docker compose up without encountering the manifest error.

For more details, you can refer to the similar issue here [1].

To continue talking to Dosu, mention @dosu.

@dosubot[bot] commented on GitHub (Sep 10, 2024): <!-- Greeting --> Hi @warlock8238! I'm here to help you with any bugs, questions, or contributions you have for langgenius/dify. Let's figure out the issue you're facing together. <!-- Answer --> I found a similar 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 to build the `langgenius/dify-api` Docker image from the source code: 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:** ```bash docker build -t langgenius/dify-api:0.8.0 -f api/Dockerfile . ``` This will build the `langgenius/dify-api:0.8.0` image locally, and you should be able to proceed with `docker compose up` without encountering the manifest error. For more details, you can refer to the similar issue [here](https://github.com/langgenius/dify/issues/3379) <sup>[[1]](https://github.com/langgenius/dify/issues/3379)</sup>. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.*
Author
Owner

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

This is a general network issue. Duplicated as well.

@crazywoola commented on GitHub (Sep 10, 2024): This is a general network issue. Duplicated as well.
Author
Owner

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

Hi @warlock8238! I'm here to help you with any bugs, questions, or contributions you have for langgenius/dify. Let's figure out the issue you're facing together.

I found a similar 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 to build the langgenius/dify-api Docker image from the source code:

  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:
    docker build -t langgenius/dify-api:0.8.0 -f api/Dockerfile .
    

This will build the langgenius/dify-api:0.8.0 image locally, and you should be able to proceed with docker compose up without encountering the manifest error.

For more details, you can refer to the similar issue here [1].

To continue talking to Dosu, mention @dosu.

Let me try

@warlock8238 commented on GitHub (Sep 10, 2024): > Hi @warlock8238! I'm here to help you with any bugs, questions, or contributions you have for langgenius/dify. Let's figure out the issue you're facing together. > > I found a similar 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 to build the `langgenius/dify-api` Docker image from the source code: > > 1. **Clone the Dify repository:** > ```shell > git clone https://github.com/langgenius/dify.git > ``` > 2. **Navigate to the Dify directory:** > ```shell > cd dify > ``` > 3. **Build the Docker image:** > ```shell > docker build -t langgenius/dify-api:0.8.0 -f api/Dockerfile . > ``` > > This will build the `langgenius/dify-api:0.8.0` image locally, and you should be able to proceed with `docker compose up` without encountering the manifest error. > > For more details, you can refer to the similar issue [here](https://github.com/langgenius/dify/issues/3379) [[1]](https://github.com/langgenius/dify/issues/3379). > > _To continue talking to [Dosu](https://dosu.dev), mention @dosu._ Let me try
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#5512