Skip to content

Fix issue #24010: warn about containerd separate storage path #24447

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
dvdksn wants to merge 3 commits into
base: main
Choose a base branch
from
+10 −0
Open

Fix issue #24010: warn about containerd separate storage path #24447

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
b9ed3c0
Fix issue #24010: warn about containerd separate storage path
dvdksn Mar 20, 2026
8d7c497
Fix style violations: remove bold emphasis and use stable link
dvdksn Mar 20, 2026
0964a53
Revert package-lock.json to main
dvdksn Mar 20, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions content/manuals/engine/storage/containerd.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -62,6 +62,16 @@ uncompressed layers are still de-duplicated through snapshotters. The
compressed storage adds overhead proportional to the number of images using
those layers.

> [!IMPORTANT]
> containerd uses a separate storage path from the Docker data directory.
> If you previously configured a custom data directory for Docker (for example,
> to use a different partition), containerd's storage is not automatically
> moved to that location. You need to configure containerd's data directory
> separately to avoid filling your root partition.
>
> To configure containerd's data directory, see the
> [containerd configuration documentation](https://github.com/containerd/containerd/blob/v2.2.2/docs/ops.md#base-configuration).

If disk space is constrained, consider the following:

- Regularly prune unused images with `docker image prune`
Expand Down