QuarkusIntegrationTest docker run, does not clean container after timeout

[bdevreugd-vialis]

If the docker run process takes more then 10 seconds to fully startup Quarkus, the extension will forcibly destroy the process. If the container, however, was started, it won't be cleaned up, leaving it running on the docker daemon.

quarkus/test-framework/common/src/main/java/io/quarkus/test/common/LauncherUtil.java

Line 73 in 11607b6

quarkusProcess.destroyForcibly();

If you use the --cidfile parameter on docker run, then at the end of the process you can check if that file exists and if so remove the container with docker rm -f {cidfile_contents}

These dangling containers also arrived with issue #17565, so I would prefer the cidfile cleanup over changing destroyForcibly to destroy, that way all issues that could arrive will never result in dangling containers.

[quarkus-bot]

/cc @geoand

[geoand]

I'll check it out