Making docker-in-docker builds x2 faster using Docker “cache-from” option
Gajus Kuizinas
1918

What confuses me still is, where does the caching actually happen?

If I am running the gitlab docker runner with .gitlab-ci.yml file specifiying the DIND service, then my build will essentially run inside a docker container. When the build will finish, the container is destroyed automatically by gitlab. So, next time when another build runs, where will it get the image from.. from my registry again? if yes, how is that caching?

Also, I am using docker compose to run integration tests, which actually pulls down many more images from an internal docker registry. Now on subsequent builds, I do not want that to happen and use the locally cached images. Will this solve the problem.

Would be great, if you can help understand this.

Like what you read? Give Sanjeev Mishra a round of applause.

From a quick cheer to a standing ovation, clap to show how much you enjoyed this story.