From 9e7576b056de8bc619b78eb1d42336548ccabcfd Mon Sep 17 00:00:00 2001
From: David Karlsson <35727626+dvdksn@users.noreply.github.com>
Date: Tue, 26 Sep 2023 17:59:32 +0200
Subject: [PATCH] build(hb): add note about build cache and gc

Signed-off-by: David Karlsson <35727626+dvdksn@users.noreply.github.com>
---
 content/build/hydrobuild.md | 24 ++++++++++++++++++++++++
 1 file changed, 24 insertions(+)

diff --git a/content/build/hydrobuild.md b/content/build/hydrobuild.md
index e92495d7c8..f1695265ab 100644
--- a/content/build/hydrobuild.md
+++ b/content/build/hydrobuild.md
@@ -451,3 +451,27 @@ default `docker` builder, run the following command:
 ```console
 $ docker context use default
 ```
+
+### How do I manage the build cache with Hydrobuild?
+
+You don't need to manage the builder's cache manually. The system manages it
+for you through [garbage collection](./cache/garbage-collection.md).
+
+Hydrobuild uses the following garbage collection limits:
+
+- Size: 90% of 1TB
+- Age: cache not used in the past 180 days
+- Number of build history records: 10 000
+
+Old cache is automatically removed if you hit any of these limits. You can
+check your current cache state using the [`docker buildx du`
+command](../engine/reference/commandline/buildx_du.md).
+
+To clear the builder's cache manually, you can use the [`docker buildx prune`
+command](../engine/reference/commandline/buildx_prune.md) command. This works
+like pruning the cache for any other builder.
+
+> **Note**
+>
+> Pruning Hydrobuild cache also removes the cache for other team members using
+> the same builder.