From da06fe0c758fc441d70ddee2355b03b0125ebaa8 Mon Sep 17 00:00:00 2001 From: scjane Date: Thu, 16 Feb 2017 17:15:58 +0800 Subject: [PATCH] Update aufs-driver.md (#1712) --- engine/userguide/storagedriver/aufs-driver.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/engine/userguide/storagedriver/aufs-driver.md b/engine/userguide/storagedriver/aufs-driver.md index b04a06f10e..60404dea9e 100644 --- a/engine/userguide/storagedriver/aufs-driver.md +++ b/engine/userguide/storagedriver/aufs-driver.md @@ -176,7 +176,7 @@ The `/var/lib/docker/aufs/layers/` directory contains metadata about how image layers are stacked. This directory contains one file for every image or container layer on the Docker host (though file names no longer match image layer IDs). Inside each file are the names of the directories that exist below -it in the stack +it in the stack. The command below shows the contents of a metadata file in `/var/lib/docker/aufs/layers/` that lists the three directories that are @@ -213,7 +213,7 @@ longer correspond to directory names. However, the containers thin writable layer still exists here and is stacked by AUFS as the top writable layer and is where all changes to the container are stored. The directory exists even if the container is stopped. This means that restarting a container will not -lose changes made to it. Once a container is deleted, it's thin writable layer +lose changes made to it. Once a container is deleted, its thin writable layer in this directory is deleted. ## AUFS and Docker performance