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

Minor style updates

This commit is contained in:
Usha Mandya 2020-10-20 11:18:18 +01:00 committed by GitHub
parent eb8e33f321
commit 0e8c1b63ff
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
storage/index.md
View File

@ -135,14 +135,14 @@ Some use cases for volumes include:
(such as `/var/lib/docker/volumes/<volume-name>`). (such as `/var/lib/docker/volumes/<volume-name>`).
- When your application requires high-performance I/O on Docker Desktop. Volumes - When your application requires high-performance I/O on Docker Desktop. Volumes
are stored in the Linux VM rather than the host, which means that reads and writes are stored in the Linux VM rather than the host, which means that the reads and writes
have much lower latency and higher throughput. have much lower latency and higher throughput.
- When your application requires fully native filesystem behaviour on Docker - When your application requires fully native file system behavior on Docker
Desktop. For example a database engine requires precise control over disk Desktop. For example, a database engine requires precise control over disk
flushing to guarantee transaction durability. Volumes are stored in the Linux flushing to guarantee transaction durability. Volumes are stored in the Linux
VM and can make these guarantees, whereas bind mounts are remoted to macOS or VM and can make these guarantees, whereas bind mounts are remoted to macOS or
Windows where the filesystems behave slightly differently. Windows, where the file systems behave slightly differently.
## Good use cases for bind mounts ## Good use cases for bind mounts