Details
-
Bug
-
Resolution: Done
-
Minor
-
0.9.0.Beta2
-
None
Description
Following the example from the README.md of the Debezium Kafka image, I tried this:
docker run -it --rm --link zookeeper:zookeeper debezium/kafka:0.9 watch-topic my.topic
But it fails:
WARNING: Using default BROKER_ID=1, which is valid only for non-clustered installations. Using ZOOKEEPER_CONNECT=172.17.0.2:2181 Using KAFKA_ADVERTISED_LISTENERS=PLAINTEXT://172.17.0.4:9092 The KAFKA_BROKER variable must be set, or the container must be linked to one that runs Zookeeper.
Another example
docker run -it --rm --link zookeeper:zookeeper debezium/kafka:0.9 create-topic mytop WARNING: Using default BROKER_ID=1, which is valid only for non-clustered installations. Using ZOOKEEPER_CONNECT=172.17.0.2:2181 Using KAFKA_ADVERTISED_LISTENERS=PLAINTEXT://172.17.0.4:9092 Creating new topic mytop with 1 partition(s) and 1 replica(s)... Exception in thread "main" joptsimple.UnrecognizedOptionException: partition is not a recognized option at joptsimple.OptionException.unrecognizedOption(OptionException.java:108) at joptsimple.OptionParser.handleLongOptionToken(OptionParser.java:510) at joptsimple.OptionParserState$2.handleArgument(OptionParserState.java:56) at joptsimple.OptionParser.parse(OptionParser.java:396) at kafka.admin.TopicCommand$TopicCommandOptions.<init>(TopicCommand.scala:361) at kafka.admin.TopicCommand$.main(TopicCommand.scala:44) at kafka.admin.TopicCommand.main(TopicCommand.scala)
