My milvus-standone is uploaded in my docker. But it happen that "collection not found" after docker is restart

[yourGaomu]

After I restarted the server, this error appeared, and all the original collections are gone. Also, when logging into Attu, it shows "milvue is not healthy yet".

[yourGaomu]

is my version is lower?

[yourGaomu]

I originally had a collection named "blog" which contained data. However, after I restarted the server and then ran docker restart milvue, this error appeared. I have encountered this issue twice already. Why is this happening?

[yhmo]

Version is between 2.4.8 and 2.4.17.
Seems the data is cracked, perhaps the metadata in etcd is lost.
For standalone deployed by docker compose, a normal restart should be ok for most of users:

docker compose restart

Maybe something else is done to the standalone.

[yourGaomu]

I’m used Method B for this. Since my Docker version is 26.1.3, it comes with Docker Compose pre-installed. I deployed the project using the second approach and also use it to restart the service. Additionally, I modified the docker-compose.yml file to include MinIO in the setup.
But, the project still reports errors after Docker restarts

[yhmo]

The docker-compose.yml already includes minio container.
Compare the docker-compose.yml you modified and the original docker-compose.yml file downloaded from the website. What is modified?

[yourGaomu]

I just modified the Minio connection address in it. Added user and password, and that's all.

[yhmo]

Under the directory, there should be a subdirectory named "volumes", where all the data is stored. Don't remove it.

Another possible reason is that you encountered a legacy bug. You can upgrade to the latest version of v2.5 to try again.

[yourGaomu]

Thank you for your answer. I just went to improve my other engineering tasks, which is why I am only replying now.
I will try again, and if there are any further issues, I will contact your help again.