[Bug]: TESTCONTAINERS_CHECKS_DISABLE doesn't stop alpine image from being pulled

Module

Core

Testcontainers version

1.21.3

Using the latest Testcontainers version?

Yes

Host OS

Ubuntu

Host Arch

x86

Docker version

Docker version 20.10.15, build fd82621

What happened?

When setting TESTCONTAINERS_CHECKS_DISABLE, the Alpine image is still being pulled. It is therefore necessary to set TESTCONTAINERS_TINYIMAGE_CONTAINER_IMAGE to something that my CI (Jenkins) can access, in order to pull that image. The docs state that if TESTCONTAINERS_CHECKS_DISABLE is true, this shouldn't happen

Relevant log output

09:33:21  2025-11-24T09:33:21.309+0000 [DEBUG] [TestEventLogger]     {"timestamp":"2025-11-24T09:33:20.633Z","severity":"INFO","message":"Testcontainers version: 1.21.3","process":{"thread":{"name":"Test worker"}}}
09:33:24  2025-11-24T09:33:23.561+0000 [DEBUG] [TestEventLogger]     {"timestamp":"2025-11-24T09:33:23.561Z","severity":"INFO","message":"Found Docker environment with local Unix socket (unix:///var/run/docker.sock)","process":{"thread":{"name":"Test worker"}}}
09:33:24  2025-11-24T09:33:23.736+0000 [DEBUG] [TestEventLogger]     {"timestamp":"2025-11-24T09:33:23.736Z","severity":"WARN","message":"\n********************************************************************************\nRyuk has been disabled. This can cause unexpected behavior in your environment.\n********************************************************************************","process":{"thread":{"name":"Test worker"}}}
09:33:24  2025-11-24T09:33:23.848+0000 [DEBUG] [TestEventLogger]     {"timestamp":"2025-11-24T09:33:23.848Z","severity":"INFO","message":"Pulling docker image: alpine:3.17. Please be patient; this may take some time but only needs to be done once.","process":{"thread":{"name":"Test worker"}}}
09:33:25  2025-11-24T09:33:24.983+0000 [DEBUG] [TestEventLogger]     {"timestamp":"2025-11-24T09:33:24.972Z","severity":"ERROR","message":"Error during callback","process":{"thread":{"name":"docker-java-stream-1039059310"}},"error":

Additional Information

No response

Beginne damit nachzuverfolgen, wie TESTCONTAINERS_CHECKS_DISABLE während der Initialisierung von Core verarbeitet wird und wo der Abruf des alpine:3.17-Images ausgelöst wird. Überprüfe das dokumentierte Verhalten für deaktivierte Checks anhand des gemeldeten Logs und füge Tests hinzu oder aktualisiere die Abdeckung, sodass das Alpine-Image nicht abgerufen wird, wenn die Einstellung aktiviert ist.