testcontainers / testcontainers/testcontainers-java
TC doesn't seem to pull the `selenium/standalone-firefox-debug` image
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 8.7k
- Forks
- 1.9k
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 9
Description
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!
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by inspecting BrowserWebDriverContainer and its handling of withImagePullPolicy(new DurationImagePullPolicy(DAY)); reproduce the behavior with selenium/standalone-firefox-debug:3.141.59. Confirm whether version-tagged images are refreshed as expected and add or update coverage for the observed pull-policy behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, java
- Domain
- testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100