Unable to restore snapshot v1.16.3 on Docker
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 34.7k
- Forks
- 2.7k
- Avg merge
- 1d 18h
- Merged PRs (30d)
- 187
Description
Current Behavior
I have a single node docker local setup running Qdrant 1.16.3. When uploading snapshots of the same version via http or dashboard, the snapshot cannot be restored.
- Snapshot was captured using qdrant dashboard.
- Snapshot stored on project file /.snapshots
Docker setup with volume binding:
services:
qdrant:
image: qdrant/qdrant:v1.16.3
container_name: qdrant
ports:
- "6333:6333"
- "6334:6334"
volumes:
- ./qdrant_data:/qdrant/storage
restart: always
Logs:
2026-01-21T05:12:28.756488Z INFO collection::shards::local_shard::snapshot: Restoring shard snapshot /qdrant/./storage/tmp/col-<collection_name>-recovery-JT0Pmt/0
2026-01-21T05:13:00.166973Z WARN collection::shards::replica_set: Cannot locally disable last active peer 1876334938577609 for replica
2026-01-21T05:13:00.440078Z ERROR qdrant::actix::helpers: Error processing request: Service internal error: Wal error: Can't init WAL: failed to read first-index file: expected value at line 1 column 1
2026-01-21T05:13:00.440440Z INFO actix_web::middleware::logger: 172.18.0.1 "POST /collections/<collection_name>/snapshots/upload HTTP/1.1" 500 127 "http://localhost:6333/dashboard" "Mozilla/5.0
Potentially corrupted snapshot file:
- extracting the snapshot file and inspecting
...\.snapshots\21.1.2026 v1.16.3\test_extract\0\wal\first-indexshowsnull
Steps to Reproduce
- Capture snapshot on local dashboard
- Upload snapshot via http/local dashboard
Expected Behavior
Restored collection from snapshot.
Possible Solution
Assumed it was a binding issue, but i am able to create, query collections no problem so quite confused here.
Context (Environment)
Detailed Description
Possible Implementation
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the Docker v1.16.3 flow through the dashboard or POST /collections/<collection_name>/snapshots/upload, using the described volume binding and snapshot. Inspect the extracted wal/first-index value alongside the WAL initialization error. Done means the captured snapshot restores successfully without the first-index error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, rust
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100