docker
/
docs
mirror of https://github.com/docker/docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Update index.md (#14215) 

There was no transition or clear delineation between persisted storage to in-memory storage.
This commit is contained in:
softwarepronto 2022-02-04 06:07:56 -08:00 committed by GitHub
parent 665c6ffa94
commit f5676f4557
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 7 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
storage/index.md
View File

@ -19,12 +19,15 @@ container layer. This means that:
kernel. This extra abstraction reduces performance as compared to using kernel. This extra abstraction reduces performance as compared to using
_data volumes_, which write directly to the host filesystem. _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 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_. _bind mounts_.
If you're running Docker on Windows you can also use a _named pipe_.
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 ## Choose the right type of mount