# How to cache an already built docker image?

**URL:** <https://discuss.circleci.com/t/how-to-cache-an-already-built-docker-image/25363>\
**Category:** Build Environment\
**Tags:** cache\
**Created:** [September 25, 2018, 12:43am UTC](https://discuss.circleci.com/t/how-to-cache-an-already-built-docker-image/25363 "2018-09-25T00:43:03Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![halfer](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/halfer/32/9083_2.png) [@halfer](https://discuss.circleci.com/u/halfer)\
**Post date:** [September 25, 2018, 10:03am UTC](https://discuss.circleci.com/t/how-to-cache-an-already-built-docker-image/25363/2 "2018-09-25T10:03:51Z")

</div>

I made some notes on that in this blog post:

> [@Notes on caching Docker layers in CircleCI](https://discuss.circleci.com/t/notes-on-caching-docker-layers-in-circleci/22067):
>
> I’ve been playing with Docker layer caching on the free tier, and have [written up some strategies](https://blog.jondh.me.uk/2018/04/strategies-for-docker-layer-caching-in-circleci/) I tried. There is an out-of-the-box cache device in CircleCI available to paid users, for an extra fee, but with a bit of extra work, anyone can have access to faster builds. My article is fairly discursive, since the kind of caching that is preferred will vary from one project/team to another. Long story short, it is my opinion that using an external registry was more effective than using the Circ…

---

_[View the full topic](https://discuss.circleci.com/t/how-to-cache-an-already-built-docker-image/25363)._