Question: Should we use or not testcontainer ryuk ?

[cmoulliard]

Question

Should we use or not testcontainer ryuk ? I'm asking such a question as for non tekton scenarios where users will use podman (inside the VM) to garbage collected the containers launched during the tests BUT not killed

If the answer to the question is yes; then the following ticket could help us to let ryuk to work with podman:
testcontainers/moby-ryuk#23 (comment)

[iocanel]

I think that we should use TESTCONTAINERS_RYUK_DISABLED.

Do you think that quarkus dev services are affected by this issue? Have you encountered a problem that indicates there is a problem?

[cmoulliard]

I did a test where TESTCONTAINERS_RYUK_DISABLED=false and that works too. So we will keep ryuk as it allows to remove the containers created

Example:

[maven : mvn-goals] 2023-11-10 08:15:53,156 INFO  [🐳 .io/postgres:14]] (build-52) Container docker.io/postgres:14 is starting: 63f24312c812c5671a8be768bbcdb1005a35279485f5340b515ee74cf4fd7961
[maven : mvn-goals] 2023-11-10 08:15:59,980 INFO  [🐳 .io/postgres:14]] (build-52) Container docker.io/postgres:14 started in PT7.149217S
[maven : mvn-goals] 2023-11-10 08:15:59,980 INFO  [io.qua.dev.pos.dep.PostgresqlDevServicesProcessor] (build-52) Dev Services for PostgreSQL started.
[maven : mvn-goals] 2023-11-10 08:15:59,983 INFO  [io.qua.dat.dep.dev.DevServicesDatasourceProcessor] (build-52) Dev Services for the default datasource (postgresql) started - container ID is 63f24312c812

Podman ps

[fedora@fedora38 ~]$ podman ps; podman ps -a
CONTAINER ID  IMAGE       COMMAND     CREATED     STATUS      PORTS       NAMES
CONTAINER ID  IMAGE       COMMAND     CREATED     STATUS      PORTS       NAMES

@iocanel

[cmoulliard]

Can we close it based on my last comment ? @iocanel