anchor.diff:  
   [source,bash,indent=0]
   ----
  -    $ docker run -it --name mysql -p 3306:3306 -e MYSQL_ROOT_PASSWORD=debezium -e MYSQL_USER=mysqluser -e MYSQL_PASSWORD=mysqlpw debezium/example-mysql:0.3
  -----
  -
  -This runs a new container using version {debezium-docker-label} of the `debezium/example-mysql` image, which is https://github.com/debezium/docker-images/blob/master/examples/mysql/0.1/Dockerfile[based on] the https://hub.docker.com/r/_/mysql/[mysql:5.7] image, defines and populate a sample "inventory" database, and creates a `debezium` user with password `dbz` that has the minimum privileges required by Debezium's MySQL connector. The command assigns the name `mysql` to the container so that it can be easily referenced later. The `-it` flag makes the container interactive, meaning it attaches the terminal's standard input and output to the container so that you can see what is going on in the container. The command maps port 3036 (the default MySQL port) in the container to the same port on the Docker host so that software outside of the container can connect to the database server. And finally, it also uses the `-e` option three times to set the `MYSQL_ROOT_PASSWORD`, `MYSQL_USER`, and `MYSQL_PASSWORD` environment variables to specific values.
  +    $ docker run -it --rm --name mysql -p 3306:3306 -e MYSQL_ROOT_PASSWORD=debezium -e MYSQL_USER=mysqluser -e MYSQL_PASSWORD=mysqlpw debezium/example-mysql:0.3
  +----
  +
  +This runs a new container using version {debezium-docker-label} of the `debezium/example-mysql` image, which is https://github.com/debezium/docker-images/blob/master/examples/mysql/0.1/Dockerfile[based on] the https://hub.docker.com/r/_/mysql/[mysql:5.7] image, defines and populate a sample "inventory" database, and creates a `debezium` user with password `dbz` that has the minimum privileges required by Debezium's MySQL connector. The command assigns the name `mysql` to the container so that it can be easily referenced later. The `-it` flag makes the container interactive, meaning it attaches the terminal's standard input and output to the container so that you can see what is going on in the container. The `--rm` flag instructs Docker to remove the container when it is stopped. The command maps port 3036 (the default MySQL port) in the container to the same port on the Docker host so that software outside of the container can connect to the database server. And finally, it also uses the `-e` option three times to set the `MYSQL_ROOT_PASSWORD`, `MYSQL_USER`, and `MYSQL_PASSWORD` environment variables to specific values.
   
   You should see in your terminal something like the following:
   
   [listing,indent=0,options="nowrap"]
   ----
  -    ...
  -    MySQL init process done. Ready for start up.
  -
  -    2016-06-09T15:38:14.731166Z 0 [Note] mysqld (mysqld 5.7.12-log) starting as process 1 ...
  -    2016-06-09T15:38:14.734891Z 0 [Note] InnoDB: PUNCH HOLE support available
  -    2016-06-09T15:38:14.734957Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
  -    2016-06-09T15:38:14.734976Z 0 [Note] InnoDB: Uses event mutexes
  -    2016-06-09T15:38:14.734992Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
  -    2016-06-09T15:38:14.735008Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.8
  -    2016-06-09T15:38:14.735023Z 0 [Note] InnoDB: Using Linux native AIO
  -    2016-06-09T15:38:14.735248Z 0 [Note] InnoDB: Number of pools: 1
  -    2016-06-09T15:38:14.735374Z 0 [Note] InnoDB: Using CPU crc32 instructions
  -    2016-06-09T15:38:14.740691Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
  -    2016-06-09T15:38:14.745890Z 0 [Note] InnoDB: Completed initialization of buffer pool
  -    2016-06-09T15:38:14.747038Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
  -    2016-06-09T15:38:14.758897Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
  -    2016-06-09T15:38:14.768080Z 0 [Note] InnoDB: Creating shared tablespace for temporary tables
  -    2016-06-09T15:38:14.768201Z 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
  -    2016-06-09T15:38:14.794327Z 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
  -    2016-06-09T15:38:14.795388Z 0 [Note] InnoDB: 96 redo rollback segment(s) found. 96 redo rollback segment(s) are active.
  -    2016-06-09T15:38:14.795428Z 0 [Note] InnoDB: 32 non-redo rollback segment(s) are active.
  -    2016-06-09T15:38:14.795826Z 0 [Note] InnoDB: Waiting for purge to start
  -    2016-06-09T15:38:14.846166Z 0 [Note] InnoDB: 5.7.12 started; log sequence number 12164862
  -    2016-06-09T15:38:14.846511Z 0 [Note] Plugin 'FEDERATED' is disabled.
  -    2016-06-09T15:38:14.848709Z 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
  -    2016-06-09T15:38:14.868821Z 0 [Note] InnoDB: Buffer pool(s) load completed at 160609 15:38:14
  -    2016-06-09T15:38:14.875260Z 0 [Warning] Failed to set up SSL because of the following SSL library error: SSL context is not usable without certificate and private key
  -    2016-06-09T15:38:14.875327Z 0 [Note] Server hostname (bind-address): '*'; port: 3306
  -    2016-06-09T15:38:14.875375Z 0 [Note] IPv6 is available.
  -    2016-06-09T15:38:14.875396Z 0 [Note]   - '::' resolves to '::';
  -    2016-06-09T15:38:14.875423Z 0 [Note] Server socket created on IP: '::'.
  -    2016-06-09T15:38:14.877831Z 0 [Warning] 'db' entry 'sys mysql.sys@localhost' ignored in --skip-name-resolve mode.
  -    2016-06-09T15:38:14.877887Z 0 [Warning] 'proxies_priv' entry '@ root@localhost' ignored in --skip-name-resolve mode.
  -    2016-06-09T15:38:14.879826Z 0 [Warning] 'tables_priv' entry 'sys_config mysql.sys@localhost' ignored in --skip-name-resolve mode.
  -    2016-06-09T15:38:14.894606Z 0 [Note] Event Scheduler: Loaded 0 events
  -    2016-06-09T15:38:14.895106Z 0 [Note] mysqld: ready for connections.
  -    Version: '5.7.12-log'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  MySQL Community Server (GPL)
  -----
  -
  -Notice that the MySQL server starts and stops a few times as the configuration is modified. The `mysqld: ready for connections` line reports that the MySQL server is running.
  +...
  +Initializing database
  +Database initialized
  +MySQL init process in progress...
  +Warning: Unable to load '/usr/share/zoneinfo/Factory' as time zone. Skipping it.
  +Warning: Unable to load '/usr/share/zoneinfo/iso3166.tab' as time zone. Skipping it.
  +Warning: Unable to load '/usr/share/zoneinfo/leap-seconds.list' as time zone. Skipping it.
  +Warning: Unable to load '/usr/share/zoneinfo/posix/Factory' as time zone. Skipping it.
  +Warning: Unable to load '/usr/share/zoneinfo/right/Factory' as time zone. Skipping it.
  +Warning: Unable to load '/usr/share/zoneinfo/zone.tab' as time zone. Skipping it.
  +mysql: [Warning] Using a password on the command line interface can be insecure.
  +mysql: [Warning] Using a password on the command line interface can be insecure.
  +
  +/usr/local/bin/docker-entrypoint.sh: running /docker-entrypoint-initdb.d/inventory.sql
  +mysql: [Warning] Using a password on the command line interface can be insecure.
  +
  +
  +
  +MySQL init process done. Ready for start up.
  +----
  +
  +Notice that the MySQL server starts and stops a few times as the configuration is modified. The `Ready for start up` line reports that the MySQL server is running and ready for use.
   
   [[start-mysql-command-line]]
   === Start a MySQL command line client
  
positive.code: 
  So before we start the connector, we need to create that Kafka topic where the connector can write out the database's schema history. We'll use the `debezium/kafka` image to start a container that runs the Kafka utility to create a `schema-changes.inventory` topic. 
  
  Go back to your terminal where you ran the `curl` commands against the Kafka Connect service, and run the following to create the topic:
  
  [source,bash,indent=0]
  ----
      $ docker run -it --rm --link zookeeper:zookeeper debezium/kafka:0.3 create-topic -r 1 schema-changes.inventory
  ----
  
  The command runs a container using version {debezium-docker-label} of the `debezium/kafka` image, uses `--rm` to tell Docker to remove the container when it stops, and links to the Zookeeper container so that the utility can find the Kafka broker(s). The command runs the `create-topic` utility, which by default create a topic with one partition - exactly what we want so that total order of all DDL statements is maintained. The `-r 1` argument specifies the topic should have 1 replica.
  
negative.code: 
  [source,bash,indent=0]
  ----
      $ docker run -it --rm --name kafka -p 9092:9092 --link zookeeper:zookeeper debezium/kafka:0.3
  ----
  
  [NOTE]
  