questdb / questdb/documentation
Update /deployment/docker
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 13
- Forks
- 44
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 26
Description
https://questdb.com/docs/deployment/docker/
https://questdb.com/docs/getting-started/capacity-planning/
should contain some info on how to correctly set /etc/docker/daemon,json.
I got the the fs.file-max limit is too low [current=524288, recommended=1048576] message, although ulimits were correct on the host.
creating /et/docker/daemons.json
{"default-ulimits": {
"nofile": {
"Name": "nofile",
"Hard": 1048576,
"Soft": 8096
},
"nproc": {
"Name": "nproc",
"Hard": 500,
"Soft": 500
}
}
}
and restarting docker fixed the problem by raising the ulimit in the container. nproc values and soft limit just fell from the sky ;-) your mileage my vary.
Contributor guide
No contributing guide indexed for this repository
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 with the deployment/docker and getting-started/capacity-planning pages linked in the issue, then trace them to their source files in the documentation repository. Add accurate guidance for configuring /etc/docker/daemon.json, including the relevant ulimit settings and the fs.file-max warning. Done means both pages explain the Docker configuration clearly and the example is valid JSON.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- devops, documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 72/100