build(cache): containerd required for cache backends with docker worker

Signed-off-by: David Karlsson <35727626+dvdksn@users.noreply.github.com>
This commit is contained in:
David Karlsson 2024-06-28 16:11:41 +02:00
parent e3a6339e4f
commit 6fb46d7472
2 changed files with 7 additions and 4 deletions

View File

@ -17,9 +17,9 @@ An external cache becomes almost essential in CI/CD build environments. Such
environments usually have little-to-no persistence between runs, but it's still
important to keep the runtime of image builds as low as possible.
The default `docker` driver supports the `inline` and `local` cache backends.
Other cache backends require you to select a different
[driver](../../drivers/index.md).
The default `docker` driver supports the `inline`, `local`, `registry`, and
`gha` cache backends, but only if you have enabled the [containerd image store](/desktop/containerd.md).
Other cache backends require you to select a different [driver](../../drivers/_index.md).
> **Warning**
>

View File

@ -27,11 +27,14 @@ The following table outlines some differences between drivers.
| Feature | `docker` | `docker-container` | `kubernetes` | `remote` |
| :--------------------------- | :---------: | :----------------: | :----------: | :----------------: |
| **Automatically load image** | ✅ | | | |
| **Cache export** | Inline only | ✅ | ✅ | ✅ |
| **Cache export** | ✓\* | ✅ | ✅ | ✅ |
| **Tarball output** | | ✅ | ✅ | ✅ |
| **Multi-arch images** | | ✅ | ✅ | ✅ |
| **BuildKit configuration** | | ✅ | ✅ | Managed externally |
\* _The `docker` driver doesn't support all cache export options.
See [Cache storage backends](../cache/backends/_index.md) for more information._
## Loading to local image store
Unlike when using the default `docker` driver, images built using other drivers