TC doesn't seem to pull the `selenium/standalone-firefox-debug` image

Hi,

We are constructing a BrowserWebDriverContainer and using container.withImagePullPolicy(new DurationImagePullPolicy(DAY));. Yet, I’ve just noticed that if I did a docker pull selenium/standalone-firefox-debug:3.141.59 it pulled a new version of that image and that the version I was having locally was a very old one. I checked other hosts where we run our TC-based tests and found the same.

Is there something we’re doing wrong or is this a bug? Maybe TC doesn’t pull it because the tag is a version?

Thanks!

[kiview]

Gotcha, so for your use case relying on a mutating Selenium tag, that represents the most recent browser version is important and Testcontainers needs to make sure it will pull the updated version.

We will consider this for our changes.

[vmassol]

We feel, that being explicit and aware of the used browser version is a good thing for users (also when debugging potential regression in browser versions). But we still would like to understand your use case and why you can’t specify (and update) the used tag by hand.

That’s because our Browser Support strategy states that we support only the latest version of Firefox and Chrome (see https://dev.xwiki.org/xwiki/bin/view/Community/SupportStrategy/BrowserSupportStrategy). If we have to update some pom.xml property everytime that FF or Chrome releases a new version then it becomes a maintenance nightmare so we’re very happy to push this to whoever maintains the selenium images 😃