fix: bump Qdrant pin to v1.18.1 (was v1.12.4 — downgrade panic)
Existing prod storage was written by a newer Qdrant (qdrant/qdrant:latest resolved to 1.18.1 on 2026-05-23). Pinning to 1.12.4 caused a shard-holder deserialization panic on startup because Qdrant's storage format is forward-compatible (newer reads older) but not backward.
This commit is contained in:
parent
7cc8fc5112
commit
14c47238bd
1 changed files with 1 additions and 1 deletions
|
|
@ -1,7 +1,7 @@
|
||||||
services:
|
services:
|
||||||
# Qdrant vector database for vector + sparse (BM25) storage
|
# Qdrant vector database for vector + sparse (BM25) storage
|
||||||
qdrant:
|
qdrant:
|
||||||
image: qdrant/qdrant:v1.12.4
|
image: qdrant/qdrant:v1.18.1
|
||||||
container_name: mem0-qdrant
|
container_name: mem0-qdrant
|
||||||
expose:
|
expose:
|
||||||
- "6333"
|
- "6333"
|
||||||
|
|
|
||||||
Loading…
Reference in a new issue