Compose Devservices config property misalignment.

[ivlcic]

Describe the bug

When trying to reuse volumes with the Compose Devservices, the quarkus.compose.devservices.remove-volumes=false config property should be used.
But unfortunately, testcontainers-ryuk cleans the volume on stop.

So if someone wants to preserve named container volumes between runs, both:
quarkus.compose.devservices.remove-volumes=false and quarkus.compose.devservices.ryuk-enabled=false properties must be set.

Should only the docs be updated?

Best,
Nikola

Expected behavior

The quarkus.compose.devservices.remove-volumes=false config property should always preserve container volumes.

Actual behavior

The testcontainers-ryuk cleans the volume on Quarkus stop, and the container volume is removed regardless of the quarkus.compose.devservices.remove-volumes value.

How to Reproduce?

No response

Output of uname -a or ver

Linux koshast 6.14.3-arch1-1 #1 SMP PREEMPT_DYNAMIC Sun, 20 Apr 2025 12:38:52 +0000 x86_64 GNU/Linux

Output of java -version

openjdk version "24.0.1" 2025-04-15 OpenJDK Runtime Environment (build 24.0.1) OpenJDK 64-Bit Server VM (build 24.0.1, mixed mode, sharing)

Quarkus version or git rev

3.22.3

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

Apache Maven 3.9.9 (8e8579a9e76f7d015ee5ec7bfcdc97d260186937) Maven home: /usr/share/java/maven Java version: 24.0.1, vendor: Arch Linux, runtime: /usr/lib/jvm/java-24-openjdk Default locale: en_US, platform encoding: UTF-8 OS name: "linux", version: "6.14.3-arch1-1", arch: "amd64", family: "unix"

Additional information

No response

[quarkus-bot]

/cc @geoand (devservices), @radcortez (config)

[ozangunalp]

indeed this is same for the stop-services flag.

I tried to configure ryuk in a more fine way, but it is not straightforward. (need to communicate with the ryuk container directly)

We can try to contribute that upstream and until then update the doc accordingly

[jnbdz]

Reproduced: Ryuk is registered with the project label and removes everything carrying it, so remove-volumes=false (and stop-services=false) cannot hold. It also turned out that in tests compose down never runs at JVM exit (the curated application close tasks do not run there), so Ryuk was the only cleanup. #56463 registers Ryuk only when both flags are on, and runs compose down from a shutdown hook in test mode, so with remove-volumes=false the containers are removed and the volume kept, in dev and test mode alike. @ozangunalp