Testcontainers ryuk abandoned during build without testing using Gradle

[kdubb]

Describe the bug

The ryuk container from the Testcontainers project is abandoned when building without running any tests.

We are experiencing this with Gradle, I cannot say wether this the same as for other build tools.

Also, we are using a multi-module Gradle project where we have many Quarkus micro-services under one parent project. If we build all the modules in one go, we get a ryuk container for each sub-module.

Expected behavior

Preferably ryuk containers are not started but at the very least they should be cleaned up after the build is done.

Actual behavior

Ryuk container(s) are abandoned and must be removed from docker manually.

How to Reproduce?

Run a build without testing in a Gradle single or multi-module project.

Example:

 ./gradlew build -Dquarkus.profile=prod -Dquarkus.container-image.build=true -x test -x integrationTest

Output of uname -a or ver

macOS 12

Output of java -version

Java 17

GraalVM version (if different from Java)

No response

Quarkus version or git rev

2.9.2.Final

Build tool (ie. output of mvnw --version or gradlew --version)

Gradle 7.4

Additional information

No response

[quarkus-bot]

/cc @glefloch, @quarkusio/devtools

[jskillin-idt]

I am not a developer so take my suggestion here with healthy skepticism, but this is perhaps an issue with your Docker or test setup, as Ryuk is intended to self-destruct on its own once it observes the JVM closing.

[geoand]

Is this still an issue?

[kdubb]

I will check. We had put a task in our Gradle project to kill all ryuk containers after completion; not pretty but it worked.

[kdubb]

[geoand]

Darn...

[kdubb]

I've just realized those orphaned containers are specifically from our systemTest task/configuration. It uses a Gradle nested build (a GradleBuild task in main build.gradle.kts) to build the project with the correct profile and then starts all the services using Docker Compose to runs some e2e tests.

The orphaned ryuk containers are from when it builds some of the services in the nested build. If I run the same type build as the nested build from the command line it doesn't happen.

[kdubb]

I did some more testing on this and it's the container build that causes the issue.

Running the following command orphans the ryuk containers:

./gradlew build -Dquarkus.container-image.build=true -x test

[kdubb]

I'm trying to recreate a simple multi-module Gradle project that reproduces this behavior.

[kdubb]

I've finally created a reproducer. It seems related to multi-module projects and building containers.

The first project, lib, is a java library and includes @QuarkusTests to test our common code that requires Quarkus extensions. For example, this includes common code that accesses Vault.

The second project, app, is a normal Quarkus application that includes lib to use the common code previously mentioned.

To reproduce the issue and get an orphaned ryuk container, run:

./gradlew clean build -Dquarkus.container-image.build=true

Running without tests, produces the same result:

./gradlew clean build -Dquarkus.container-image.build=true -x test

Notably, running a normal build with/without tests, using the following, will not orphan any containers:

./gradlew clean build

code-with-quarkus.zip

[geoand]

Thanks for the thorough analysis!

I'll have a look

[geoand]

The reproducer was most helpful!

#28702 fixes the issue

[jorsol]

Just a comment here:

The ryuk container can be disabled by setting the env var TESTCONTAINERS_RYUK_DISABLED=true

https://www.testcontainers.org/features/configuration/#disabling-ryuk