In a previous life, I set up CI runner images (Amazon AMIs) that had all of our docker base images pre-cached, and ran custom docker cleanup script that exclude

In a previous life, I set up CI runner images (Amazon AMIs) that had all of our docker base images pre-cached, and ran custom docker cleanup script that excluded images with certain tags. This meant that a new runner would be relatively quick off the blocks, and get faster as it built/pulled more images. You can get better cache hit from tagging your gitlab runners and pinning projects to certain tags. Also this: https://medium.com/titansoft-engineering/docker-build-cache-sharing-on-multi-hosts-with-buildkit-and-buildx-eb8f7005918e https://medium.com/titansoft-engineering/docker-build-cache-... ... Sharing cache on multiple hosts using buildkit + buildx