Tests: follow up on pinning cp-kafka docker image to 6.2.1

[simonbasle]

On December 10th, CI started to fail. Digging down into the issue, it appeared that Testcontainers was unable to start the cp-kafka Docker image unless it was pinned to an older version, 6.2.1. Leaving the default version (latest) or pinning both to 7.0.1 and 6.2.2 failed.

Finally, pinning the cp-kafka Docker image to 6.2.1 did the trick.

The Testcontainers team is using the same version in their integration tests. They've been made aware and will investigate the Kafka testcontainers integration with newer images (TBD link to issue).

This issue is there to track the fact that the image version is pinned.

Git log of attempts made to get to the root cause / find a fix

• Increase TestContainers Timeout
• Revert timeout; trace logging for TC
• Limit to 1 test; --debug; remove quotes from paths for capture
• Try explicit cp-kafka version 7.0.1
• Try 6.2.2; 7.0.1 is same as latest; just one test method.
• Remove --debug.
• Upgrade TestContainers to 1.16.2
• bump log4j
• try to get just enough logs with standardOut output, force showStanda…
• Try with disabling Ryuk
• back to default cp-kafka version
• Include a second non-testcontainers test
• reactivate ryuk, but try OS ubuntu-18.04
• Quick and dirty bump to Gradle 7 see if it changes something
• try with cp-kafka 6.2.1