# Docker layer cache for CI

Coming soon. Docker layer caching is in development and is not available yet.

## Use case: repeat a container build

Once available, add a buildx step using RZV_DOCKER_CACHE_DIR. A later run of the same trusted ref on the same host will reuse matching layers while its cache is retained. Changed inputs rebuild affected layers. Check build output for CACHED on unchanged steps. No speedup is guaranteed.

## Workspace and repository boundaries

Caches will separate workspaces, repositories and trust levels. Untrusted runs will use per-attempt scopes. The design keeps fork pull requests and other untrusted jobs out of any cache that trusted builds read. Concurrent jobs will use separate disk copies. The last completed snapshot will replace the earlier one.

## Cold builds remain normal

The cache will be disposable, size-limited and subject to eviction. A different host will start cold. Shared cache reuse across hosts is not available. Never store secrets or the only copy of your data in a build cache.

## Availability and billing

Saving a cache preference does not turn caching on. No price has been announced. Keep your working build workflow until caching is available for your workspace. Check this page for status. We have not set a launch date.

## Related pages and language

[Buildx example](https://runzivo.dev/docs/docker-layer-cache-example/)

[Français (Canada)](https://runzivo.dev/docs/docker-layer-cache-fr-ca/)

On this page and page tools