Windows, docker: incorrect data inserted
Open
Nobody has claimed this yet.
Docker
Windows
- Dominant language
- Java
- Stars
- 17.3k
- Forks
- 1.6k
- Avg merge
- 5d 10h
- Merged PRs (30d)
- 28
Description
To reproduce
Run on windows 11 pro, docker desktop v4.28
docker run -t -i -v C:\Volumes\QuestDB:/var/lib/questdb -p 9000:9000 -p 9009:9009 -p 8812:8812 -p 9003:9003 --restart=always --net=docker-net --name=questdb questdb/questdb:8.1.1
Using web console run
See value inserted as 0. See logs
QuestDB version:
8.1.1
OS, in case of Docker specify Docker and the Host OS:
Windows 11 Pro, docker
File System, in case of Docker specify Host File System:
NTFS
Full Name:
Alex Pelagenko
Affiliation:
QuestDB
Have you followed Linux, MacOs kernel configuration steps to increase Maximum open files and Maximum virtual memory areas limit?
- Yes, I have
Additional context
Note: this is a user-reported issue, to be reproduced
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 reported insert on Windows 11 Pro with Docker Desktop 4.28, the questdb/questdb:8.1.1 image, and an NTFS-mounted volume using the command in the issue. Inspect the linked logs and compare the inserted value with the expected value; done means identifying the cause of the zero value and documenting a verified correction or reproduction result.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100