@rose_1001
I’m glad to hear that it seems to have been resolved.
If your fix worked, the issue may have been related to the file system permissions, ACL, SELinux, or similar mechanisms on your Docker host.
Also, Docker might be running in rootless mode.
Anyway, normally, there shouldn’t be any issues with everyday use if you use a named volume (weaviate_data:/var/lib/weaviate) instead of bind mount (./volumes/weaviate:/var/lib/weaviate).
However, if you ever consider file-based backing up or restoring your environment, please note that your files for Weaviate are not inside the ./volumes/weaviate directory on your Docker host. Be aware of this point.
Enjoy!