> Once you’ve got your images fine, but if your build nodes are elastic you can easily hit cold/new nodes and pay the penalty. If you have your own Nexus or Ar

> Once you’ve got your images fine, but if your build nodes are elastic you can easily hit cold/new nodes and pay the penalty. If you have your own Nexus or Artifactory, or even just a registry that's configured as a pull through cache (https://docs.docker.com/registry/recipes/mirror/ https://docs.docker.com/registry/recipes/mirror/), then it shouldn't be a problem. If those two servers are in an internal network, even better, otherwise just get a VPS with a good port speed. Honestly, even 100 Mbps should be enough for 2 GB, taking less than 30 seconds, with 1 Gbps that time becomes 2 seconds: https://techinternets.com/copy_calc https://techinternets.com/copy_calc The difference here would be that you're using your own software on your own servers and therefore can deal with the load that you generate yourself with the full allotment of resources that you have, vs having to rely on public registries that are used by tens of thousands of other developers/processes at the same time. That's not that different from S3 either (apart from maybe more capacity being available to you on private buckets, depending on the vendor), since you can also use something like MinIO or Zenko on your own servers as well instead of relying on the cloud.