Documentation
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. Fork pull requests and other untrusted jobs never fill a cache read by trusted builds. Concurrent jobs will use separate disk copies. The last completed snapshot will replace the earlier one.
Cold builds remain normal
The cache is disposable, size-limited and subject to eviction. A different host starts 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 enable caching. No new cache charge is active and no cache price is published. Keep your working build workflow until caching is enabled and verified for your workspace.