Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add prereqs to AUFS configuration steps #1067

Merged
merged 2 commits into from
Jan 18, 2017
Merged

Add prereqs to AUFS configuration steps #1067

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
3129d07
Add prereqs to AUFS configuration steps
Jan 9, 2017
a49449e
Add the info about the linux-image-extra packages
Jan 9, 2017
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
63 changes: 39 additions & 24 deletions engine/userguide/storagedriver/aufs-driver.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -97,43 +97,58 @@ back to a "copy and unlink" strategy.

## Configure Docker with AUFS

### Prerequisites

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.

$ grep aufs /proc/filesystems
```bash
$ grep aufs /proc/filesystems

nodev aufs
```

nodev aufs
This output indicates the system supports AUFS. If you get no output, your system does
not support AUFS. You can address this by upgrading your host system's kernel to 3.13
or higher. It is recommended to intall the kernel headers when you upgrade.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Don't think it's in the kernel by default, and the linux-image-extra kernel package is needed (at least on Ubuntu)

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oops, you are right. I missed that. Have a look now.


This output indicates the system supports AUFS. Once you've verified your
system supports AUFS, you can must instruct the Docker daemon to use it. You do
this from the command line with the `dockerd` command:
### Configuration

$ sudo dockerd --storage-driver=aufs &
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`:

```bash
$ sudo dockerd --storage-driver=aufs &
```

Alternatively, you can edit the Docker config file and add the
To make the change permanent, you can edit the Docker configuration file and add the
`--storage-driver=aufs` option to the `DOCKER_OPTS` line.

# Use DOCKER_OPTS to modify the daemon startup options.
DOCKER_OPTS="--storage-driver=aufs"
```none
# Use DOCKER_OPTS to modify the daemon startup options.
DOCKER_OPTS="--storage-driver=aufs"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

not related, but looks like we need to update this as well, to use the daemon.json approach

```

Once your daemon is running, verify the storage driver with the `docker info`
command.
After the daemon starts, verify the default storage driver using the `docker info`
command:

$ sudo docker info
```bash
$ sudo docker info

Containers: 1
Images: 4
Storage Driver: aufs
Root Dir: /var/lib/docker/aufs
Backing Filesystem: extfs
Dirs: 6
Dirperm1 Supported: false
Execution Driver: native-0.2
...output truncated...
Containers: 1
Images: 4
Storage Driver: aufs
Root Dir: /var/lib/docker/aufs
Backing Filesystem: extfs
Dirs: 6
Dirperm1 Supported: false
Execution Driver: native-0.2
...output truncated...
```

The output above shows that the Docker daemon is running the AUFS storage
driver on top of an existing `ext4` backing filesystem.
Look for the `Storage Driver` line. If its value is `aufs`, the Docker daemon is
using the AUFS storage driver on top of the filesystem listed on the
`Backing Filesystem` line.

## Local storage and AUFS

Expand Down Expand Up @@ -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)
* [Select a storage driver](selectadriver.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)