You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Docker Desktop is transitioning to use containerd for image and filesystem management. This page outlines the benefits, setup process, and new capabilities enabled by the containerd image store.
12
-
13
-
> [!NOTE]
14
-
>
15
-
> Docker Desktop maintains separate image stores for the classic and containerd image stores.
16
-
> When switching between them, images and containers from the inactive store remain on disk but are hidden until you switch back.
11
+
Docker Desktop uses containerd as its image store by default. The image store
12
+
is the component responsible for pushing, pulling, and storing images on your
13
+
filesystem. The containerd image store supports features like multi-platform
14
+
images, image attestations, and alternative snapshotters.
17
15
18
16
## What is `containerd`?
19
17
20
-
`containerd` is a container runtime that provides a lightweight, consistent interface for container lifecycle management. It is already used under the hood by Docker Engine for creating, starting, and stopping containers.
21
-
22
-
Docker Desktop’s ongoing integration of containerd now extends to the image store, offering more flexibility and modern image support.
18
+
`containerd` is a container runtime that provides a lightweight, consistent
19
+
interface for container lifecycle and image management. It is used under the
20
+
hood by Docker Engine for creating, starting, and stopping containers.
23
21
24
22
## What is the `containerd` image store?
25
23
26
24
The image store is the component responsible for pushing, pulling,
27
25
and storing images on the filesystem.
28
26
29
-
The classic Docker image store is limited in the types of images that it supports.
30
-
For example, it doesn't support image indices, containing manifest lists.
31
-
When you create multi-platform images, for example,
32
-
the image index resolves all the platform-specific variants of the image.
33
-
An image index is also required when building images with attestations.
34
-
35
27
The containerd image store extends the range of image types
36
28
that the Docker Engine can natively interact with.
37
29
While this is a low-level architectural change,
@@ -47,20 +39,33 @@ it's a prerequisite for unlocking a range of new use cases, including:
0 commit comments