docker
/
docs
mirror of https://github.com/docker/docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #20802 from dvdksn/c8d-default 

desktop: containerd default store for 4.34 fresh installs
This commit is contained in:
David Karlsson 2024-09-09 10:12:18 +02:00 committed by GitHub
parent 630a2a2bfa 6d7712bbdd
commit b65c890150
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
4 changed files with 23 additions and 17 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
content/desktop/containerd.md
View File

@ -10,10 +10,9 @@ image and file system management in the Docker Engine.
> [!NOTE] > [!NOTE]
> >
> After switching to the containerd image store, > Images and containers are not shared between the classic image store and the
> images and containers in the classic image store won't be visible. > new containerd image store. When you switch image stores, containers and
> All of those containers and images still exist. > images from the inactive store remain but are hidden until you switch back.
> To see them again, turn off the containerd image store feature.
## What is containerd? ## What is containerd?
@ -53,8 +52,13 @@ it's a prerequisite for unlocking a range of new use cases, including:
## Enable the containerd image store ## Enable the containerd image store
The containerd image store isn't enabled by default. The containerd image store is enabled by default in Docker Desktop version 4.34
To enable the feature for Docker Desktop: and later, but only for clean installs or if you perform a factory reset. If
you upgrade from an earlier version of Docker Desktop, or if you use an older
version of Docker Desktop you must manually switch to the containerd image
store.
To manually enable this feature in Docker Desktop:
1. Navigate to **Settings** in Docker Desktop. 1. Navigate to **Settings** in Docker Desktop.
2. In the **General** tab, check **Use containerd for pulling and storing images**. 2. In the **General** tab, check **Use containerd for pulling and storing images**.

6
content/desktop/wasm.md
View File

@ -184,14 +184,14 @@ This section contains instructions on how to resolve common issues.
### Unknown runtime specified ### Unknown runtime specified
If you try to run a Wasm container before you have opted in to use the If you try to run a Wasm container without the [containerd image
containerd image store, an error similar to the following displays: store](./containerd.md), an error similar to the following displays:
```text ```text
docker: Error response from daemon: Unknown runtime specified io.containerd.wasmedge.v1. docker: Error response from daemon: Unknown runtime specified io.containerd.wasmedge.v1.
``` ```
[Turn on the containerd feature](containerd.md#turn-on-the-containerd-image-store-feature) [Turn on the containerd feature](./containerd.md#enable-the-containerd-image-store)
in Docker Desktop settings and try again. in Docker Desktop settings and try again.
### Failed to start shim: failed to resolve runtime path ### Failed to start shim: failed to resolve runtime path

9
content/scout/how-tos/view-create-sboms.md
View File

@ -75,10 +75,11 @@ $ docker build --tag <org>/<image> \
--push . --push .
``` ```
To build images with SBOM attestations, you must either turn on To build images with SBOM attestations, you must use either the [containerd
the [containerd image store](/desktop/containerd.md) feature, or use a image store](/desktop/containerd.md) feature, or use a `docker-container`
`docker-container` builder together with the `--push` flag to push the image builder together with the `--push` flag to push the image (with attestations)
(with attestations) directly to a registry. directly to a registry. The classic image store doesn't support manifest lists
or image indices, which is required for adding attestations to an image.
## Extract to file ## Extract to file

9
content/scout/quickstart.md
View File

@ -204,12 +204,13 @@ built so that it can provide a better evaluation result.
Before you can build an image with attestations, Before you can build an image with attestations,
you must enable the [containerd image store](../desktop/containerd.md) you must enable the [containerd image store](../desktop/containerd.md)
(or create a custom builder using the `docker-container` driver). (or create a custom builder using the `docker-container` driver).
The default image store doesn't support manifest lists, The classic image store doesn't support manifest lists,
which is how the provenance attestations are attached to an image. which is how the provenance attestations are attached to an image.
Open **Settings** in Docker Desktop. Under the **General** section, Open **Settings** in Docker Desktop. Under the **General** section, make sure
check the **Use containerd for pulling and storing images** option. that the **Use containerd for pulling and storing images** option is checked.
Note that changing the image store hides existing images and containers until you switch back. Note that changing image stores temporarily hides images and containers of the
inactive image store until you switch back.
With the containerd image store enabled, rebuild the image with a new `v3` tag. With the containerd image store enabled, rebuild the image with a new `v3` tag.
This time, add the `--provenance=true` and `--sbom=true` flags. This time, add the `--provenance=true` and `--sbom=true` flags.