From 4c23e132f88dc706cfa8a2278a3e74868de39926 Mon Sep 17 00:00:00 2001 From: Misty Stanley-Jones Date: Thu, 30 Mar 2017 15:13:44 -0700 Subject: [PATCH] Clarify missing parent images (#2566) Fixes #636 --- engine/userguide/storagedriver/imagesandcontainers.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/engine/userguide/storagedriver/imagesandcontainers.md b/engine/userguide/storagedriver/imagesandcontainers.md index c90dbf068f..c896be0c22 100644 --- a/engine/userguide/storagedriver/imagesandcontainers.md +++ b/engine/userguide/storagedriver/imagesandcontainers.md @@ -338,9 +338,10 @@ command. > **Note**: Under the content addressable storage model introduced with Docker > 1.10, image history data is no longer stored in a config file with each image > layer. It is now stored as a string of text in a single config file that -> relates to the overall image. This can result in some image layers showing as -> "missing" in the output of the `docker history` command. This is normal -> behavior and can be ignored. +> relates to the overall image. This can result in some parent image layers showing as +> `missing` in the output of the `docker history` command. This is normal +> behavior and can be ignored. `missing` means that there is no local image +> associated with this history chain. > > You may hear images like these referred to as *flat images*.