Kevin Hu
Kevin Hu
No, it always supports.
This file is missing. 
I guess that page from 1 to 277 was too much for your server to take, and it restarted after failure.
`export MAX_CONCURRENT_CHATS=10` Or, pull the `nightly` version of docker image.
`docker logs -f ragflow-es-01`
`no such key` is a warning log which can be ignored. Check the status of redis. 
Warning message could be ignored.
What is the name of the local image? change it to `RAGFLOW_IMAGE`.
Pulling the `nightly` version of docker image to upgrade to latest code.
Never **`-v`** ``` docker compose down -v ``` This will remove all data. Otherwise, data is still there.