From 3c117d8e64d7601512f8c92c3348f96ebd5eeb82 Mon Sep 17 00:00:00 2001 From: Michael Lipovka Date: Tue, 1 Sep 2026 13:58:22 +0300 Subject: [PATCH] docs: correct DOCKER_MIGRATE_SNAPSHOTTER_THRESHOLD description The threshold is a human-readable total image layer size, not an image count. Update the example and explanation accordingly. Fixes docker/docs#25914 --- content/manuals/engine/storage/containerd.md | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/content/manuals/engine/storage/containerd.md b/content/manuals/engine/storage/containerd.md index 64bacd22b080..cb771285b32a 100644 --- a/content/manuals/engine/storage/containerd.md +++ b/content/manuals/engine/storage/containerd.md @@ -138,7 +138,8 @@ To enable automatic migration, add the `containerd-migration` feature to your You can also set the `DOCKER_MIGRATE_SNAPSHOTTER_THRESHOLD` environment variable to make the daemon switch automatically if you have no containers and -your image count is at or below the threshold. For systemd: +the total size of all image layers is at or below the threshold. The value is a +human-readable size (for example, `200M` or `1G`). For systemd: ```console $ sudo systemctl edit docker.service @@ -148,11 +149,12 @@ Add: ```ini [Service] -Environment="DOCKER_MIGRATE_SNAPSHOTTER_THRESHOLD=5" +Environment="DOCKER_MIGRATE_SNAPSHOTTER_THRESHOLD=200M" ``` -If you have no running or stopped containers and 5 or fewer images, the daemon -switches to the containerd image store on restart. Your overlay2 data remains +If you have no running or stopped containers and the total size of all image +layers is 200M or less, the daemon switches to the containerd image store on +restart. Your overlay2 data remains on disk but becomes hidden. ## Additional resources