v0.22.0 image not being downloaded after running docker compose

[alspires]

Hello,

I noticed that now, on v0.22.0's compose file, we have 2 different services: ragflow-cpu and ragflow-gpu. I've tried starting up both with compose, but for some reason none are downloading Ragflow's image so I can run the UI locally.

Is this intended behavior, am I missing something else that has changed in this latest version?

Thanks.

[dosubot[bot]]

This isn't intended behavior, but it's likely due to a change in how images are published and referenced in v0.22.0. Both ragflow-cpu and ragflow-gpu use the image specified by the RAGFLOW_IMAGE environment variable, which defaults to infiniflow/ragflow:v0.22.0 in docker/.env. If this variable isn't set or is set incorrectly, Docker Compose won't pull the image details.

Starting with v0.22.0, only a slim version of the image is published (without the -slim suffix), and embedding models are no longer included in the main image see PR #11190. If you're having trouble pulling the image, check that RAGFLOW_IMAGE in docker/.env is set to infiniflow/ragflow:v0.22.0. If you still can't pull the image, you can try using a mirror registry as suggested in the README.

If Docker Compose gives you a specific error, sharing that output could help pinpoint the issue.

To reply, just mention @dosu.

---

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

[alspires]

@dosu The command being run + the outputs I get are below:

docker compose --profile opensearch --env-file .env --env-file ./local/ragflow/docker/.env up -d  --remove-orphans
WARN[0000] The "UID" variable is not set. Defaulting to a blank string.
WARN[0000] The "GID" variable is not set. Defaulting to a blank string.
[+] Running 70/70
 ✔ pgadmin Pulled                                                                                       13.5s
 ✔ redis Pulled                                                                                         18.2s
 ✔ localstack Pulled                                                                                    30.8s
 ✔ opensearch01 Pulled                                                                                  62.7s
 ✔ postgres Pulled                                                                                      25.4s
[+] Running 5/5
 ✔ Container expc_ragflow-opensearch01-1  Started                                                        1.0s
 ✔ Container expc_ragflow-redis-1         Started                                                        1.1s
 ✔ Container expc_ragflow-postgres-1      Started                                                        0.9s
 ✔ Container expc_ragflow-pgadmin-1       Started                                                        1.0s
 ✔ Container expc_ragflow-localstack-1    Started                                                        1.2s

As you can see, there is no Ragflow container being created and no image being downloaded. I have checked and the RAGFLOW_IMAGE is being set correctly on Ragflow's own .env file.

[dosubot[bot]]

The reason the Ragflow container isn't being created is that your command only activates the opensearch profile, but the Ragflow services (ragflow-cpu and ragflow-gpu) are assigned to the cpu and gpu profiles, respectively. To start Ragflow, you need to add --profile cpu (or --profile gpu) to your Docker Compose command details.

However, even with the correct profile, the infiniflow/ragflow:v0.22.0 image is not currently available on Docker Hub or the other registries, so Docker Compose can't pull it details.

Workarounds:

• Use the nightly image from a mirror registry by setting RAGFLOW_IMAGE in your .env to one of:

  swr.cn-north-4.myhuaweicloud.com/infiniflow/ragflow:nightly
  registry.cn-hangzhou.aliyuncs.com/infiniflow/ragflow:nightly
  

• Build the image locally and set RAGFLOW_IMAGE to your local tag.
• Use v0.21.1 if you need a stable release.

Let me know if you want step-by-step instructions for any of these options.

To reply, just mention @dosu.

---

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