- Raise a bug report
- Raise a support issue
- Raise a feature request
- View our knowledge base of resolved issues
Does Kpow run on Apple Silicon (arm64)?
Yes! We push a multi-arch build to Dockerhub which supports both linux/amd64 and linux/arm64 platforms.
Apple Silicon (M1) support should work out of the box. If it doesn't try the following command:
docker run --platform=linux/arm64 --pull=always -p 3000:3000 -m 2G factorhouse/kpow-ce:latest
Kpow starts but times out connecting to my Kafka cluster
Are you running your Kafka cluster on your local machine (non-Dockerized)?
You might need the command:
docker run --net=host --pull=always -p 3000:3000 -m 2G factorhouse/kpow-ce:latest
The --net=host option is used to make the programs inside the Docker container look like they are running on the host itself, from the perspective of the network. It allows the container greater network access than it can normally get.
Are you running your Kafka cluster in another Docker network (Docker Compose etc)?
First, find out the name of your Docker network (usually compose_default for Compose):
docker network ls
Then run the command:
docker run --net=compose_default --pull=always -p 3000:3000 -m 2G factorhouse/kpow-ce:latest
More information here
Do you have a Docker Compose example?
Yes! If you want to run Kpow with a 3-node cluster and Kafka Connect view our kpow-local GitHub repository.
Getting started instructions can be found in the README.
Does Kpow support truststore certificates when connecting to Kafka?
Yes! Use a Docker volume mount to attach your truststore certificates from your local machine:
docker run --volume="$PWD/certs:/opt/kpow/certs" --pull=always -p 3000:3000 -m 2G factorhouse/kpow-ce:latest
The above example will mount a local directory named certs to /opt/kpow/certs inside the running Kpow container instance.
What are the memory requirements?
We suggest 1G memory as a minimum, 2G for normal deployments, 4G for production.
docker run --pull=always -p 3000:3000 -m 2G factorhouse/kpow-ce:latest