Guide for running with clickhouse docker
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- clickhouse, docker, docker-compose
- Domain
- databases, devops, documentation
Research direction
Start with docker-compose.yml and the ClickHouse Docker command and environment variables shown in the report; reproduce the localhost:9000 failures from the compose services on macOS M1. Done means documenting a working ClickHouse setup and guidance for the reported app, worker, and web proxy errors.
Written by the indexing model from the issue text.
Description
I think a guide would be nice -- for some reason I can't get this to connect to my local clickhouse instance running on docker.
How I'm starting docker instance (on macOS m1 chip):
docker run -d -p 8123:8123 -p 9000:9000 \
-v "$(pwd)/ch_data":/var/lib/clickhouse/ \
-v "$(pwd)/ch_logs":/var/log/clickhouse-server/ \
-v "$(pwd)/config.d":/etc/clickhouse-server/config.d/ \
--name local-clickhouse --ulimit nofile=262144:262144 \
-e CLICKHOUSE_DB=my_database -e CLICKHOUSE_USER=username -e CLICKHOUSE_DEFAULT_ACCESS_MANAGEMENT=1 -e CLICKHOUSE_PASSWORD=1234 \
clickhouse/clickhouse-server
How I start housewatch:
CLICKHOUSE_HOST=localhost \
CLICKHOUSE_CLUSTER=local-clickhouse \
CLICKHOUSE_USER=username \
CLICKHOUSE_PASSWORD=1234 \
CLICKHOUSE_SECURE=false \
docker compose -f docker-compose.yml up
Resulting errors
housewatch-app-1 | Failed to connect to localhost:9000
housewatch-worker-1 | Failed to connect to localhost:9000
housewatch-web-1 |
housewatch-web-1 | Proxy error: Could not proxy request /api/analyze/hostname from localhost:3000 to http://localhost:8000.
housewatch-web-1 | See https://nodejs.org/api/errors.html#errors_common_system_errors for more information (ECONNREFUSED).
housewatch-web-1 |
Would love any insights.
- Dominant language
- TypeScript
- Stars
- 634
- Forks
- 46
- PR merge metrics
- No merged PRs in 30d
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- No contributing 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.
More from PostHog/HouseWatch
-
Monitor mutationsOpen
Difficulty 5/5 Over a week Newbie friendliness 30/100
PostHog/HouseWatch#82 ·
-
fist time running HouseWatchMay be free again A pull request for this issue was closed without being merged. Open
Difficulty 4/5 3-5 days Newbie friendliness 25/100
PostHog/HouseWatch#80 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
PostHog/HouseWatch#76 · 3 reactions ·
-
schema stats page error on loading dataMay be free again A pull request for this issue was closed without being merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 48/100
PostHog/HouseWatch#70 · 2 comments · 1 reaction ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 42/100
PostHog/HouseWatch#64 ·
All issues in PostHog/HouseWatch
Similar issues
-
enhancement needs peer review
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
pnp/cli-microsoft365#7696 ·
Maintainers usually reply within 3 days
-
Add: AutomotoOpencheck:passed streams:add
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
inmanta/web-console#7899 ·
Maintainers usually reply within 1 day