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

remove aufs "default storage driver" statements 

In many cases, aufs is no longer the default storage driver, so just change the example to not mention the default. If you'd like it to actually state overlay2 is the default in most/some cases I can change that.
This commit is contained in:
Bret Fisher 2018-09-27 04:11:47 -04:00 committed by GitHub
parent 718784351c
commit 4b39f91fb0
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/storagedriver/index.md
View File

@ -143,8 +143,8 @@ Status: Downloaded newer image for ubuntu:15.04
Each of these layers is stored in its own directory inside the Docker host's Each of these layers is stored in its own directory inside the Docker host's
local storage area. To examine the layers on the filesystem, list the contents local storage area. To examine the layers on the filesystem, list the contents
of `/var/lib/docker/<storage-driver>/layers/`. This example uses `aufs`, which of `/var/lib/docker/<storage-driver>/layers/`. This example uses the `aufs`
is the default storage driver: storage driver:
```bash ```bash
$ ls /var/lib/docker/aufs/layers $ ls /var/lib/docker/aufs/layers
@ -292,8 +292,8 @@ layer. This means that the writable layer is as small as possible.
When an existing file in a container is modified, the storage driver performs a When an existing file in a container is modified, the storage driver performs a
copy-on-write operation. The specifics steps involved depend on the specific copy-on-write operation. The specifics steps involved depend on the specific
storage driver. For the default `aufs` driver and the `overlay` and `overlay2` storage driver. For the `aufs`, `overlay` and `overlay2` drivers, the
drivers, the copy-on-write operation follows this rough sequence: copy-on-write operation follows this rough sequence:
* Search through the image layers for the file to update. The process starts * Search through the image layers for the file to update. The process starts
at the newest layer and works down to the base layer one layer at a time. at the newest layer and works down to the base layer one layer at a time.