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.

从 org.testcontainers.images.RemoteDockerImage 开始，尤其是 resolve，并使用 Docker 的 --iidfile 输出中的本地镜像 ID 重现报告的案例。确认 docker run 接受 sha256 镜像 ID，然后验证完成后的行为会使用现有的本地镜像，而不是尝试从 registry 拉取。