Doing some funky Docker Compose stuff, including:

See also docs. To help future Googlers… with the Confluent docker images for Kafka, KSQL, Kafka Connect, etc, if you want to access JMX metrics from within, you just need to pass two environment variables: <x>_JMX_HOSTNAME and <x>_JMX_PORT, prefixed by a component name. <x>_JMX_HOSTNAME - the hostname/IP of the JMX host machine, as accessible from the JMX Client. This is used by the JMX client to connect back into JMX, so must be accessible from the host machine running the JMX client.

(This was cross-posted on the Confluent.io blog)

---

This question comes up on StackOverflow and such places a lot, so here’s something to try and help.

tl;dr : You need to set advertised.listeners (or KAFKA_ADVERTISED_LISTENERS if you’re using Docker images) to the external address (host/IP) so that clients can correctly connect to it. Otherwise they’ll try to connect to the internal host address–and if that’s not reachable then problems ensue.

Put another way, courtesy of Spencer Ruport:

LISTENERS are what interfaces Kafka binds to. ADVERTISED_LISTENERS are how clients can connect.

(Previously, previously, previously) Since Proxmox 4 has a recent Linux kernel and mainline one at that, it means that Docker can be run on it. I’ve yet to really dig into Docker and work out when it makes sense in place of Linux Containers (LXC), so this is going to be a learning experience for me. To install Docker, add Backports repo to apt: root@proxmox01:~# cat /etc/apt/sources.list.d/backports.list deb http://ftp.debian.org/debian jessie-backports main And then install:

After a long and painful delivery, I’m delighted to announce the arrival of a new addition to my household … : This custom-build from Scan 3XS is sat in my study quietly humming away. I’m going to use it for hosting VMs for R&D on OBIEE, Big Data Lite, Elastic, InfluxDB, Kafka, etc. I’ll blog various installations that I’ve done on it as a reference for myself, and anyone else interested.