Starting version 1.16.1 over 1.16.0 via Docker results in a startup panic. The data is stored in a mounted volume residing on Windows, while the container uses the official Qdrant Docker image.
Current Behavior
Crash at startup
Steps to Reproduce
- Start a container using v1.16.0 with a mounted volume as data folder
- Create a collection
- Add some data
- Stop the instance
- Change the docker image version to v1.16.1
- Start the instance
Docker compose file
services:
qdrant:
image: qdrant/qdrant:v1.16.1
ports:
- 6333:6333
- 6334:6334
expose:
- 6333
- 6334
volumes:
- ./qdrant_data:/qdrant/storageCollection config.json as found in storage
{"params":{"vectors":{"fast-bge-small-en-v1.5":{"size":384,"distance":"Cosine"}},"shard_number":1,"replication_factor":1,"write_consistency_factor":1,"on_disk_payload":true},"hnsw_config":{"m":16,"ef_construct":100,"full_scan_threshold":10000,"max_indexing_threads":0,"on_disk":false},"optimizer_config":{"deleted_threshold":0.2,"vacuum_min_vector_number":1000,"default_segment_number":0,"max_segment_size":null,"memmap_threshold":null,"indexing_threshold":10000,"flush_interval_sec":5,"max_optimization_threads":null},"wal_config":{"wal_capacity_mb":32,"wal_segments_ahead":0,"wal_retain_closed":1},"quantization_config":null,"uuid":null}payload_index.json
{"schema":{"document":{"type":"text","tokenizer":"word","min_token_len":2,"max_token_len":15,"lowercase":true}}}shard_key_mapping.json
version.info
Expected Behavior
Qdrant starts
Possible Solution
Context (Environment)
Here the startup log
_ _
__ _ __| |_ __ __ _ _ __ | |_
/ _` |/ _` | '__/ _` | '_ \| __|
| (_| | (_| | | | (_| | | | | |_
\__, |\__,_|_| \__,_|_| |_|\__|
|_|
Version: 1.16.1, build: e293ab1f
Access web UI at http://localhost:6333/dashboard
2025-11-25T18:16:18.291709Z ERROR qdrant: Filesystem check failed for storage path ./storage. Details: Unrecognized filesystem - cannot guarantee data safety
2025-11-25T18:16:18.294311Z INFO storage::content_manager::consensus::persistent: Loading raft state from ./storage/raft_state.json
2025-11-25T18:16:18.316296Z INFO storage::content_manager::toc: Loading collection: changes
2025-11-25T18:16:19.541856Z ERROR qdrant::startup: Panic backtrace:
0: qdrant::startup::setup_panic_hook::{{closure}}
1: std::panicking::panic_with_hook
2: std::panicking::panic_handler::{{closure}}
3: std::sys::backtrace::__rust_end_short_backtrace
4: __rustc::rust_begin_unwind
5: core::panicking::panic_fmt
6: collection::shards::shard_holder::ShardHolder::load_shards::{{closure}}
7: collection::collection::Collection::load::{{closure}}
8: storage::content_manager::toc::TableOfContent::new
9: qdrant::main
10: std::sys::backtrace::__rust_begin_short_backtrace
11: main
12: <unknown>
13: __libc_start_main
14: _start
2025-11-25T18:16:19.541908Z ERROR qdrant::startup: Panic occurred in file /qdrant/lib/collection/src/shards/replica_set/mod.rs at line 315: Failed to load local shard "./storage/collections/changes/0": Service internal error: Failed to load mutable full text index from gridstore: Service runtime error: Failed to deserialize document: invalid type: integer `0`, expected struct StoredDocument
Detailed Description
Possible Implementation
Starting version 1.16.1 over 1.16.0 via Docker results in a startup panic. The data is stored in a mounted volume residing on Windows, while the container uses the official Qdrant Docker image.
Current Behavior
Crash at startup
Steps to Reproduce
Docker compose file
Collection
config.jsonas found in storage{"params":{"vectors":{"fast-bge-small-en-v1.5":{"size":384,"distance":"Cosine"}},"shard_number":1,"replication_factor":1,"write_consistency_factor":1,"on_disk_payload":true},"hnsw_config":{"m":16,"ef_construct":100,"full_scan_threshold":10000,"max_indexing_threads":0,"on_disk":false},"optimizer_config":{"deleted_threshold":0.2,"vacuum_min_vector_number":1000,"default_segment_number":0,"max_segment_size":null,"memmap_threshold":null,"indexing_threshold":10000,"flush_interval_sec":5,"max_optimization_threads":null},"wal_config":{"wal_capacity_mb":32,"wal_segments_ahead":0,"wal_retain_closed":1},"quantization_config":null,"uuid":null}payload_index.json{"schema":{"document":{"type":"text","tokenizer":"word","min_token_len":2,"max_token_len":15,"lowercase":true}}}shard_key_mapping.jsonversion.infoExpected Behavior
Qdrant starts
Possible Solution
Context (Environment)
Here the startup log
Detailed Description
Possible Implementation