Add prereqs to AUFS configuration steps

Fixes #1061
This commit is contained in:
Misty Stanley-Jones 2017-01-09 10:21:14 -08:00 committed by GitHub
parent 9b96144191
commit 3129d0737a
1 changed files with 39 additions and 24 deletions

View File

@ -97,43 +97,58 @@ back to a "copy and unlink" strategy.
## Configure Docker with AUFS ## Configure Docker with AUFS
### Prerequisites
You can only use the AUFS storage driver on Linux systems with AUFS installed. You can only use the AUFS storage driver on Linux systems with AUFS installed.
Use the following command to determine if your system supports AUFS. Use the following command to determine if your system supports AUFS.
$ grep aufs /proc/filesystems ```bash
$ grep aufs /proc/filesystems
nodev aufs nodev aufs
```
This output indicates the system supports AUFS. Once you've verified your This output indicates the system supports AUFS. If you get no output, your system does
system supports AUFS, you can must instruct the Docker daemon to use it. You do not support AUFS. You can address this by upgrading your host system's kernel to 3.13
this from the command line with the `dockerd` command: or higher. It is recommended to intall the kernel headers when you upgrade.
$ sudo dockerd --storage-driver=aufs & ### Configuration
When you have verified that you meet the prerequisites, instruct the Docker daemon to use
AUFS by starting the Docker daemon with the flag `--storage-driver=aufs`:
Alternatively, you can edit the Docker config file and add the ```bash
$ sudo dockerd --storage-driver=aufs &
```
To make the change permanent, you can edit the Docker configuration file and add the
`--storage-driver=aufs` option to the `DOCKER_OPTS` line. `--storage-driver=aufs` option to the `DOCKER_OPTS` line.
# Use DOCKER_OPTS to modify the daemon startup options. ```none
DOCKER_OPTS="--storage-driver=aufs" # Use DOCKER_OPTS to modify the daemon startup options.
DOCKER_OPTS="--storage-driver=aufs"
```
Once your daemon is running, verify the storage driver with the `docker info` After the daemon starts, verify the default storage driver using the `docker info`
command. command:
$ sudo docker info ```bash
$ sudo docker info
Containers: 1 Containers: 1
Images: 4 Images: 4
Storage Driver: aufs Storage Driver: aufs
Root Dir: /var/lib/docker/aufs Root Dir: /var/lib/docker/aufs
Backing Filesystem: extfs Backing Filesystem: extfs
Dirs: 6 Dirs: 6
Dirperm1 Supported: false Dirperm1 Supported: false
Execution Driver: native-0.2 Execution Driver: native-0.2
...output truncated... ...output truncated...
```
The output above shows that the Docker daemon is running the AUFS storage Look for the `Storage Driver` line. If its value is `aufs`, the Docker daemon is
driver on top of an existing `ext4` backing filesystem. using the AUFS storage driver on top of the filesystem listed on the
`Backing Filesystem` line.
## Local storage and AUFS ## Local storage and AUFS
@ -227,4 +242,4 @@ needs to detect its failure and fall back to a "copy and unlink" strategy.
* [Understand images, containers, and storage drivers](imagesandcontainers.md) * [Understand images, containers, and storage drivers](imagesandcontainers.md)
* [Select a storage driver](selectadriver.md) * [Select a storage driver](selectadriver.md)
* [Btrfs storage driver in practice](btrfs-driver.md) * [Btrfs storage driver in practice](btrfs-driver.md)
* [Device Mapper storage driver in practice](device-mapper-driver.md) * [Device Mapper storage driver in practice](device-mapper-driver.md)