Cant start docker compose: => ERROR [web 3/3] COPY build/ build/
Nobody has claimed this yet.
- #93 by @vaibhavmashal — closed without merging
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 40/100
Research direction
Start with docker-compose.yml and the web service's Dockerfile/build context; verify whether build/ is generated or present before COPY build/ build/. Reproduce with docker compose -f docker-compose.yml up and compare the external CLICKHOUSE_HOST setup after removing depends_on. Done means startup no longer fails at the web COPY step and supports the stated external ClickHouse configuration.
Written by the indexing model from the issue text.
Description
The default docker-compose.yml has an incorrect ref to "clickhouse" service. Should this be removed? I have a clickhouse cluster deployed in AWS and I am providing the hostname via the Env vars:
SITE_ADDRESS=:80 \
CLICKHOUSE_HOST=<AWS ALB hostname>\
CLICKHOUSE_CLUSTER=mycluster \
CLICKHOUSE_USER= <someusername> \
CLICKHOUSE_PASSWORD=xxxxxxxxxxx \
docker compose -f docker-compose.yml up
After removing the reference of "clickhouse" service under the depends_on section, the docker instances fails to start with the following error:
=> CANCELED [worker 1/8] FROM docker.io/library/python:3.10@sha256:1a8dcc07368065c2b285b24236a98e80355d6de7f685b416407aafb6dd32529f 0.5s
=> => resolve docker.io/library/python:3.10@sha256:1a8dcc07368065c2b285b24236a98e80355d6de7f685b416407aafb6dd32529f 0.0s
=> => sha256:aa51dc5b3e4b04c28168c424bb88a7329fa5ddea735617e70aca8e276bed838a 7.53kB / 7.53kB 0.0s
=> => sha256:00046d1e755ea94fa55a700ca9a10597e4fac7c47be19d970a359b0267a51fbf 0B / 24.03MB 0.4s
=> => sha256:9f13f5a53d118643c1f1ff294867c09f224d00edca21f56caa71c2321f8ca004 0B / 64.11MB 0.4s
=> => sha256:1a8dcc07368065c2b285b24236a98e80355d6de7f685b416407aafb6dd32529f 1.65kB / 1.65kB 0.0s
=> => sha256:17b967fa748a2929eb2682018a9d0e335aeebff3963469e901b67544bd01be49 2.01kB / 2.01kB 0.0s
=> => sha256:012c0b3e998c1a0c0bedcf712eaaafb188580529dd026a04aa1ce13fdb39e42b 0B / 49.56MB 0.4s
=> [worker internal] load build context 0.0s
=> => transferring context: 3.49kB 0.0s
=> [app internal] load build context 0.0s
=> => transferring context: 3.49kB 0.0s
=> CACHED [web 1/3] FROM docker.io/library/alpine:latest@sha256:7144f7bab3d4c2648d7e59409f15ec52a18006a128c733fcff20d3a4a54ba44a 0.0s
=> [web internal] load build context 0.0s
=> => transferring context: 2B 0.0s
=> [web 2/3] WORKDIR /frontend 0.0s
=> ERROR [web 3/3] COPY build/ build/ 0.0s
------
> [web 3/3] COPY build/ build/:
------
failed to solve: failed to compute cache key: failed to calculate checksum of ref b31f82cc-6f48-4507-bec3-385667894ed8::e8fy1zrfjzzwwtfpwoj97s5ac: "/build": not found
Am I doing something wrong? The error message indicates that there is an issue with the COPY command in the Dockerfile. What would be the next steps to resolve this?
- 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