Internal Registry doesn't work

To avoid race limit in dockerhub, we put postgres image into our internal jfrog and try to fetch from there. We run the test case on jenkins worker and we can pull the internal image from jenkins worker without any issue. So I don't have clue why the testcontainers still seeing the docker hub limits issue.

Code:
private static final PostgreSQLContainer postgres = new PostgreSQLContainer(
DockerImageName.parse("symphony-docker-local.artifactory.eng.vmware.com/postgres:12.0")
.asCompatibleSubstituteFor("postgres"));

Error:

Caused by: org.testcontainers.containers.ContainerFetchException: Can't get Docker image: RemoteDockerImage(imageName=symphony-docker-local.artifactory.eng.vmware.com/postgres:12.0, imagePullPolicy=DefaultPullPolicy())
	at org.testcontainers.containers.GenericContainer.getDockerImageName(GenericContainer.java:1278) ~[testcontainers-1.15.0.jar:na]
	at org.testcontainers.containers.GenericContainer.logger(GenericContainer.java:612) ~[testcontainers-1.15.0.jar:na]
	at org.testcontainers.containers.GenericContainer.doStart(GenericContainer.java:317) ~[testcontainers-1.15.0.jar:na]
	... 62 common frames omitted
Caused by: com.github.dockerjava.api.exception.InternalServerErrorException: Status 500: {"message":"toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit"}

Riprodurre il test di Jenkins-worker usando PostgreSQLContainer con DockerImageName.parse e asCompatibleSubstituteFor("postgres"). Tracciare il percorso di recupero dell’immagine attorno a GenericContainer e l’eccezione Docker Java segnalata, quindi verificare che l’immagine JFrog configurata venga scaricata senza ricorrere a Docker Hub né attivarne il rate limit.