From f5676f4557414487cb68aaf60acb3ea7dd46f8dc Mon Sep 17 00:00:00 2001 From: softwarepronto Date: Fri, 4 Feb 2022 06:07:56 -0800 Subject: [PATCH] Update index.md (#14215) There was no transition or clear delineation between persisted storage to in-memory storage. --- storage/index.md | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-) diff --git a/storage/index.md b/storage/index.md index 685004b030..6103ea1f54 100644 --- a/storage/index.md +++ b/storage/index.md @@ -19,12 +19,15 @@ container layer. This means that: kernel. This extra abstraction reduces performance as compared to using _data volumes_, which write directly to the host filesystem. -Docker has two options for containers to store files in the host machine, so +Docker has two options for containers to store files on the host machine, so that the files are persisted even after the container stops: _volumes_, and -_bind mounts_. If you're running Docker on Linux you can also use a _tmpfs mount_. -If you're running Docker on Windows you can also use a _named pipe_. +_bind mounts_. -Keep reading for more information about these two ways of persisting data. +Docker also supports containers storing files in-memory on the the host machine. Such files are not persisted. +If you're running Docker on Linux, _tmpfs mount_ is used to store files in the host's system memory. +If you're running Docker on Windows, _named pipe_ is used to store files in the host's system memory. + +Keep reading for more information about persisting data or taking advantage of in-memory files. ## Choose the right type of mount