From e59b50b43b1952975fd8fcf61fdd7375cf43c86e Mon Sep 17 00:00:00 2001 From: caisah Date: Sun, 15 Nov 2020 14:05:46 +0200 Subject: [PATCH] Fix typo --- basic_concept/image.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/basic_concept/image.md b/basic_concept/image.md index c54683a..94dbe62 100644 --- a/basic_concept/image.md +++ b/basic_concept/image.md @@ -6,7 +6,7 @@ Docker Image is a special filesystem. Apart from programs, libs, resources and c ## Advanced Multi-layered Unification Filesystem (AUFS) -Because the image contains the complete `root` file system of the operating system, its volume is often huge. So Docker made full use of [Union FS](https://en.wikipedia.org/wiki/Union_mount) and was designed as AUFS when it was designed. So strictly speaking, image is not a packaged file like an ISO iamge file. Image is just a virtual concept. It is not composed of a single file, but a group of file systems, or a combination of multi-layered filesystems. +Because the image contains the complete `root` file system of the operating system, its volume is often huge. So Docker made full use of [Union FS](https://en.wikipedia.org/wiki/Union_mount) and was designed as AUFS when it was designed. So strictly speaking, image is not a packaged file like an ISO image file. Image is just a virtual concept. It is not composed of a single file, but a group of file systems, or a combination of multi-layered filesystems. When building an image, it builds layer by layer, and the former is the basis for the latter. Once each layer is built, it will not change later. Any change on the latter layer will only occur on its own level. For example, deleting the previous layer of files is not really deleting the files, but only marked as deleted in the current layer. When the final container runs, you won't see the file, but in fact the file will always follow the image. Therefore, take more care when building the image, and any redundant file should be cleared up in ahead of the layer's final construction.