Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Running docker test env with Confluent docker quickstart #38

Open
sshanks-kx opened this issue Jun 8, 2020 · 1 comment
Open

Running docker test env with Confluent docker quickstart #38

sshanks-kx opened this issue Jun 8, 2020 · 1 comment
Assignees

Comments

@sshanks-kx
Copy link
Contributor

When using this env
https://docs.confluent.io/current/quickstart/ce-docker-quickstart.html

Add doc to detail how to get a kdb q instance to talk to the above env (given that the above is setup to communicate with each other inside the env)

@sshanks-kx sshanks-kx self-assigned this Jun 8, 2020
@sshanks-kx
Copy link
Contributor Author

Run the above env.
After start-up, can run

docker network ls
docker network inspect cp-all-in-one_default

to see the new network configured & hosts running within it

When running a separate docker image containing kdb/Kafka libs, in order to talk to the above network add the following to your docker run cmd
--network cp-all-in-one_default
That your container within the same network so it can talk to the hosts with broker/zookeeper/etc.

Then your docker image needs to use
broker:29092
as the broker to connect to.

NOTE: when running your own docker container, if you need to open another shell to it, can run the likes of ...
docker exec -it <docker container name> /bin/bash

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant