Image Name Substitution not applied for DockerComposeContainers

I have a set of tests which create a DockerComposeContainer on startup. I ran into the below error when the tests run on a CI server:

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"}

First, I tried setting a hub.image.name.prefix to point to my company's local registry, but continued to run into the error. I next tried creating a custom ImageNameSubstitutor to redirect images to my company's local registry, but that did not seem to help either. I then tried changing all image names in my docker-compose file to point at the local registry, and that seemed to resolve my problems.

I could be wrong, but I suspect this is because the image substitution mechanism is called from RemoteDockerImage, which is not used when parsing docker-compose files. My build logs seem to indicate that the ryuk and socat images are correctly being pulled from the local registry, but not the images referenced in the compose file.

Is this intended behavior? I don't see any references to docker-compose on the documentation page about image substitution.

Inizia dalla gestione delle immagini di DockerComposeContainer e confrontala con il percorso ImageNameSubstitutor utilizzato da RemoteDockerImage. Riproduci il caso CI con limite della frequenza dei pull usando un registry personalizzato e un file Compose, quindi verifica che le immagini referenziate da Compose vengano reindirizzate in modo coerente e che la documentazione sulla sostituzione delle immagini rifletta questo comportamento.