Cannot use against local image Ids

For example, if using the output of --iidfile then the image is attempted to be fetched instead of using the existing local image Id:

Caused by: org.testcontainers.containers.ContainerFetchException: Retry limit reached while trying to pull image: sha256:8cf620617c6203b24af7c5bf15a7212386c27ad008fc4c6ff7e37a1bf0a3cdd2
	at org.testcontainers.images.RemoteDockerImage.resolve(RemoteDockerImage.java:91)
	at org.testcontainers.images.RemoteDockerImage.resolve(RemoteDockerImage.java:25)
	at org.testcontainers.utility.LazyFuture.getResolvedValue(LazyFuture.java:20)
	at org.testcontainers.utility.LazyFuture.get(LazyFuture.java:27)
	at org.testcontainers.containers.GenericContainer.getDockerImageName(GenericContainer.java:839)
	... 55 more
Caused by: com.github.dockerjava.api.exception.NotFoundException: {"message":"pull access denied for sha256, repository does not exist or may require 'docker login'"}

docker run --it --rm sha256:8cf620617c6203b24af7c5bf15a7212386c27ad008fc4c6ff7e37a1bf0a3cdd2 works as expected.

Commencez par org.testcontainers.images.RemoteDockerImage, en particulier resolve, et reproduisez le cas signalé en utilisant un ID d’image local provenant de la sortie de --iidfile de Docker. Confirmez que docker run accepte l’ID d’image sha256, puis vérifiez que le comportement final utilise l’image locale existante au lieu de tenter un pull depuis le registre.