many-solstice-66904
01/30/2023, 9:22 AM./docker/dev.sh script to get started on local development. When I do this I run into the following issue:
+ docker-compose -f docker-compose.yml -f docker-compose.override.yml -f docker-compose.dev.yml pull
[+] Running 9/12
⠿ zookeeper Pulled 1.2s
⠿ broker Pulled 1.2s
⠿ elasticsearch-setup Warning 1.5s
⠿ kafka-setup Warning 1.7s
⠿ mysql Pulled 1.2s
⠿ datahub-actions Pulled 1.3s
⠿ mysql-setup Pulled 1.4s
⠿ datahub-frontend-react Warning 1.5s
⠿ neo4j Pulled 1.3s
⠿ datahub-gms Pulled 1.4s
⠿ schema-registry Pulled 1.4s
⠿ elasticsearch Pulled 1.2s
WARNING: Some service image(s) must be built from source by running:
docker compose build datahub-frontend-react elasticsearch-setup kafka-setup
3 errors occurred:
* Error response from daemon: manifest for linkedin/datahub-frontend-react:debug not found: manifest unknown: manifest unknown
* Error response from daemon: manifest for linkedin/datahub-elasticsearch-setup:debug not found: manifest unknown: manifest unknown
* Error response from daemon: manifest for linkedin/datahub-kafka-setup:debug not found: manifest unknown: manifest unknown
running COMPOSE_DOCKER_CLI_BUILD=1 DOCKER_BUILDKIT=1 DOCKER_DEFAULT_PLATFORM="$(uname -m)" docker-compose -p datahub -f docker-compose.yml -f docker-compose.override.yml -f docker-compose.dev.yml build kafka-setup exits with exit code 0 so that works fine. My local build also succeeds with no issues. I've had a look through the documentation and this channel but I have not found an issue similar to this so I am at a bit of a loss what to do here.bulky-electrician-72362
01/30/2023, 9:43 AM:debug
https://github.com/datahub-project/datahub/blob/master/docker/docker-compose.dev.yml#L15
This needs to be built with --build as here: https://github.com/datahub-project/datahub/blob/master/docker/dev.sh#L36bulky-electrician-72362
01/30/2023, 9:44 AMmany-solstice-66904
01/30/2023, 9:54 AMCOMPOSE_DOCKER_CLI_BUILD=1 DOCKER_BUILDKIT=1 DOCKER_DEFAULT_PLATFORM="$(uname -m)" docker-compose -p datahub -f docker-compose.yml -f docker-compose.override.yml -f docker-compose.dev.yml up --build instead of ./dev.sh does start up the docker-compose! Thanks!many-solstice-66904
01/30/2023, 9:58 AM./dev.sh and running the command in my previous messagemany-solstice-66904
01/30/2023, 3:23 PM./dev.sh the compose starts up but I encounter various errors, mostly along the lines of connection refused:
broker | [2023-01-30 15:12:19,394] INFO Socket connection established, initiating session, client: /172.22.0.6:49622, server: zookeeper/172.22.0.3:2181 (org.apache.zookeeper.ClientCnxn)
broker | [2023-01-30 15:12:19,410] INFO Session establishment complete on server zookeeper/172.22.0.3:2181, sessionid = 0x1000013d5f60004, negotiated timeout = 6000 (org.apache.zookeeper.ClientCnxn)
broker | [2023-01-30 15:12:19,417] INFO [ZooKeeperClient Kafka server] Connected. (kafka.zookeeper.ZooKeeperClient)
kafka-setup | [kafka-admin-client-thread | adminclient-1] WARN org.apache.kafka.clients.NetworkClient - [AdminClient clientId=adminclient-1] Connection to node -1 (broker/172.22.0.6:29092) could not be established. Broker may not be available.
broker | [2023-01-30 15:12:19,853] INFO Cluster ID = yIs4V-aYRlGx6hUBVaiwLw (kafka.server.KafkaServer)
broker | [2023-01-30 15:12:19,865] ERROR Fatal error during KafkaServer startup. Prepare to shutdown (kafka.server.KafkaServer)
broker | kafka.common.InconsistentClusterIdException: The Cluster ID yIs4V-aYRlGx6hUBVaiwLw doesn't match stored clusterId Some(tdMvimAORMKeYVuotsChWw) in meta.properties. The broker is trying to join the wrong cluster. Configured zookeeper.connect may be wrong.many-solstice-66904
01/31/2023, 8:38 AM./docker/dev.sh script with docker-compose v1.29.2 fixed it. (previously used docker compose v2.*)bulky-electrician-72362
01/31/2023, 9:59 AMstrong-easter-55319
02/08/2023, 11:53 AMThis install scenario is no longer supported.
many-solstice-66904
02/08/2023, 12:00 PM