Reaper image does not start when using HUB_IMAGE_NAME_PREFIX

[robertcoltheart]

Expected Behaviour
When setting the TESTCONTAINERS_HUB_IMAGE_NAME_PREFIX value to an Artifactory registry, I would expect the target container as well as the reaper container to use this registry to pull and run images.

Actual Behaviour
It seems there is a bug in isReaper() where it compares the current image (which has the full image name prefix) against the name of the reaper image (without the image prefix) and will go into an endless loop. See here.

eg.

this.imageName.string: artifactory.mycompany.com:100/testcontainers/ryuk:0.11.0
REAPER_IMAGE: testcontainers/ryuk:0.11.0

It should either compare the current image with the reaper image without the prefix for both, or with the prefix for both.

Testcontainer Logs
Logs hang on "waiting for file lock".

Steps to Reproduce

1. In this environment...
2. With this config...
3. Run '...'
4. See error...

Environment Information

• Operating System:
• Docker Version:
• Node version:
• Testcontainers version:

[robertcoltheart]

I think there was some issue with my environment, I don't think this is a bug after all. Apologies.