-/docs/disabling-codefresh-caching-mechanisms/

toc:true

Docker builds can be optimized by caching images and layers used during the build.

Codefresh facilitates two kinds of caches:

Docker builds can be optimized by caching images and layers used during the build.Codefresh facilitates two kinds of caches:

1. Docker engine (local) cache: building images that reuseunchangedlayers, oruses`FROM` statements forimages thatarealready exists, will benefit from the docker engine cache,justas when buildingin your local workstation. Codefresh takes care of persisting the cache and making it availble for the current pipeline execution environment.

2. Last build cache: Codefresh will intelligently pull the last image builtfor the cuurent project/branch/commitand will use that when building the image using Docker's`--cache-from` build option. This optimization also reduces build times for most scenarios.

1. Docker engine (local) cache: building images that reuse layers orare based onimages that already exists will benefit from the docker engine cache fulfilling those dependencies immediately (justlike when buildingon your local workstation). Codefresh takes care of persisting the docker cache and making it availble for the current pipeline execution environment.

2. Last build cache: Codefresh will intelligently pull the last imagesuccessfullybuilt and will use that when building the image using Docker's`--cache-from` build option. This optimization reduces build times for most scenarios.

You can choose to opt out of each cache mechanism, both at the step definition level, or temporarily at the build execution level.

In the Build execution dialog, click on the "Advanced Options" button, under "More Options", selectthe appropriate checkbox to ignore dockercacheor cf cache.

In the Build execution dialog, click on the "Advanced Options" button, under "More Options", select"Ignore Codefreshcacheoptimizations for build".