What are the rules that RunPod follows to cache DockerHub images?
I did some more testing today and it seems like RunPod sometimes holds a copy of my docker image, which leads to the fast load I'm looking for. Is there any predictability to this? Like, is it cached for a specified amount of time?
10 Replies
There is no predictability. Images that are used more often have a higher chance of being cached. But if you're using your own image, there is a very low chance of it being cached because there are different machines even within the same data center, so if its cached on one machine in the data center, its not cached on others.
Makes sense -- do you know if there are future plans to enable some more predictability on this, whether that's via defining caching, or even storing images in the network storage?
Im not sure, check it on #🧐｜feedback
YES! They could offer users a container repo like DO does but on network. Combine that with S3 storage we are REALLY talking then!
Write it on feedbacks
I don't think its really possible with RunPod because they have data centers and hosts all over the world, not just within a region.
If they could offer it, it would probably only be possible with secure cloud and not community cloud.
Have you heard the term "physician heal thyself"? RunPod could deploy this and others easily using their own infrastructure. Just need to run one or more persistent containers on each serverless runpod host. Then they could provide any number of services for their customers. Since such services would not consume GPU running them would not impact availability for users.
"their own infrastructure", Community cloud is NOT their own infrastructure.
Also serverless only uses secure cloud not community cloud.
Ok, they could provide such services in secure cloud then? That would be awesome! 🙂 I don't mean to be snarky I just see the potential.
i think its not really possible since runpod handles the containers handling
and you don't get much control over the hosts