

It’s a quick and easy option and works well for most use cases I’ve come across. The most reliable solution I’ve come across so far is to alias to the loopback 0 interface: sudo ifconfig lo0 alias $CONTAINER_IP


Docker for mac 17.06 trial#
It wasn’t the first time I had experienced service-container communication issues and a huge hint was of course the fact that this seemed to work seamlessly on Linux.Īfter many headaches, investigation, trial and error here are a few solutions I’ve gathered and tested that could be of help to you too. Producers and consumers could be started easily from within the containers and communicate between themselves at that level.Īs soon as I attempted to establish a connection between the local UPS instance and the Kafka broker, however, all communication seemed to come to a standstill.Īlthough the application could connect to the broker on its published port and the topics were being created, the messages sent from the UPS were not being properly published and the consumer wasn’t reading anything back. The most straightforward and uncomplicated solution was running the UPS locally, while Zookeeper and the Kafka broker would run in two separate Docker containers.įrom the very beginning I ran into loads of issues.
Docker for mac 17.06 code#
When Google Summer of Code first began, one of our first tasks was describing the steps for the required Kafka-Zookeeper setup. Docker for Mac networking ←Home Subscribe Docker for Mac networking
