What is the caching mechanism of RUNPOD docker image?

our Docker image is stored in AWS ECR. We've noticed that every time we update the Docker template on the runpod, our ECR costs increase rapidly. We've identified that this is due to using 80 runpod instances, and these runpod instances concurrently pull the image. We would like to inquire about the image caching mechanism of runpod. If we let one runpod instance pull the Docker image completely first before starting other instances, will the other instances pull the image from your cache instead of AWS ECR?