Closed fokot closed 7 years ago
Which docker executor you are using? If Spotify
one, then it doesn't support container links I think
Ah, this might be a reason, I use Spotify one
I ran into the same issue when I had to switch from the DockerJava executor to the Spotify one (the spotify implementation has better/correct AuthConfig).
I created a pull which enables container linking when using the Spotify docker executor, see https://github.com/whisklabs/docker-it-scala/pull/62
Btw, in my experience using the LogLineContains ready checker for Kafka isn't working properly. I'm running a custom ready checker that uses a ZooKeeper client to check the brokers have registered:
.withReadyChecker(
DockerReadyChecker.F { _ ⇒
zookeeperAddress.map { address ⇒
val zkUtils = ZkUtils(
address.getHostName + ":" + address.getPort,
10.seconds.toMillis.toInt,
10.seconds.toMillis.toInt,
false
)
val hasBrokers = zkUtils.getChildren("/brokers/ids").nonEmpty
zkUtils.close()
hasBrokers
}
}
.looped(nrOfReadyCheckRetries, readyCheckDuration)
)
There is a latest working example with container linking introduced here https://github.com/whisklabs/docker-it-scala/pull/74/files
I'm trying to run Kafka with Zookeeper like this:
Kafka always times out in connecting to zookeeper. I even set StartContainersTimeout to 60 seconds, didn't help. But running from docker-compose is without problem. What this an be?