Welcome to ksqlDB-GraphQL-poc Discussions!

[gklijs]

👋 Welcome!

We’re using Discussions as a place to connect with other members of our community. We hope that you:

• Ask questions you’re wondering about.
• Share ideas.
• Engage with other community members.
• Welcome others and are open-minded. Remember that this is a community we
  build together 💪.

To get started, comment below with an introduction of yourself and tell us about what you do with this community.

[frostcs7]

docker-compose up is throwing this stacktrace:
ksqldb | [kafka-admin-client-thread | adminclient-1] WARN org.apache.kafka.clients.NetworkClient - [AdminClient clientId=adminclient-1] Connection to node -1 (kafka/172.18.0.3:19092) could not be established. Broker may not be available.

[gklijs]

How do you run docker-compose?

[frostcs7]

@gklijs In the root folder running.
docker-compose up please lemme know in case we need to startup in different manner ))

[gklijs]

I meant, which platform, where does your docker run? I'm not even 100% sure for this one, but almost sure it used to work on an Intel MacBook pro, using Docker desktop.

[frostcs7]

Intel MacBook pro on mac darwin OS using docker desktop :(

[gklijs]

Now that I look better, I think it should be fine, as eventually Kafka should be up. Properly waiting can be a bit of pain with docker compose, so it just keeps restarting the failing containers. After a few minutes, is it still giving that error?

[frostcs7]

Lemme try again!

[gklijs]

Sounds good, I think you just need to be a bit more patient still. It's possible to improve, by having the containers wait till other ones are healthy/available. In which case you don't see these errors, but it's not easy.

[yazan9]

Running into the same problem as the error above. I've waited for ~10 minutes but the error persists. I tried both branches, main and persons branch.
Tried with Docker Desktop on Windows 11 though ...

[gklijs]

I could try to take a look next weekend.

[yazan9]

thanks @gklijs !

[gklijs]

Turned out the schema-setter did need the confluent repo since the plugin has regular dependencies. That should fix that problem, but I did see some other ones. A queue full from the data creator. However, as ksqlDB might be EOL soon, and because I'm not interested in it anymore, I don't want to spend more time on it.
The fix was just pushed to all two branches.

[yazan9]

Thanks @gklijs for your follow up.