Bug report

The DebeziumContainer waits for a known log message pattern during startup. However, there is a race and this message can be printed before Kafka Connect REST interface is up. As the result a GET request to /connectors returns HTTP 404.

This race is not visible on reasonably fast computers, but it's occasionally visible when running a Debezium Intel-only image container on M1 ARM under emulation.

What behaviour do you expect?

I'd expect the wait strategy to stop waiting once after the container is fully started and initialized, including Kafka Connect REST interface.

Do you have the connector logs, ideally from start till finish?

yes

Implementation ideas (optional)

Use HTTP WaitStrategy instead. The container will not be considered as started until /connectors returns HTTP 200