Details
-
Task
-
Resolution: Fixed
-
Major
-
12.6.6, 12.10.2
-
None
-
Unknown
-
N/A
-
N/A
-
Description
See https://github.com/testcontainers/testcontainers-java/releases/tag/1.15.1
In 1.15.0, ImageNameSubstitutor was added to help dealing with Docker Hub's rate limits. 1.15.1 introduces a default implementation that automatically prefixes every image without the registry. See the docs for more details.
Could maybe fix our issue:
Caused by: com.github.dockerjava.api.exception.DockerClientException: Could not pull image: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit at com.github.dockerjava.api.command.PullImageResultCallback.checkDockerClientPullSuccessful(PullImageResultCallback.java:97) at com.github.dockerjava.api.command.PullImageResultCallback.throwFirstError(PullImageResultCallback.java:112) at com.github.dockerjava.api.async.ResultCallbackTemplate.awaitCompletion(ResultCallbackTemplate.java:93) at org.xwiki.test.docker.internal.junit5.DockerTestUtils.startContainer(DockerTestUtils.java:154)
Selenium: Restore getDockerImageForCapabilities method to public scope (#3441) @rnorth
We can remove our reflection hack!
Attachments
Issue Links
- is related to
-
XINFRA-331 Rate limit reach for pulling docker images in the xwiki docker-based test framework
- Closed