Docker w/ AUFS doesn't work on top BTRFS filesystem

[dysinger]

I was asked to file this but it's probably a dupe of other requests for BTRFS support

Reproduce:
1 - Install Ubuntu 13.04 fresh with BTRFS filesystem
2 - Install Docker from PPA
3 - Pull busybox
4 - Try to start it

Code barfs at https://github.com/dotcloud/docker/blob/master/image.go#L137 with "Unable to mount aufs"

[vieux]

Thanks, @dysinger

Can you test #826 and tell me if it fixes your issue ?

[creack]

#826 and #885 fixes all known issue on btrfs/xfs systems :)

[mhennings]

I still encounter some "stale nfs handles" from time to time when running on btrfs.

I am not able to reproduce it, but it happens often enough to switch the container base directory to a ext4 partition.

[djmaze]

Same problem over here. Can reliably reproduce the error as follows (prompt shortened).

$ docker run -i -t base /bin/bash
(inside the container)
$ apt-get update
$ apt-get -y install wget
$ wget ftp://ftp.ruby-lang.org/pub/ruby/2.0/ruby-2.0.0-p247.tar.bz2
$ tar xvjf ruby-2.0.0-p247.tar.bz2
$ cd ruby-2.0.0-p247
$ ./configure
pwd: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
configure: error: working directory cannot be determined
$ ls
ls: cannot open directory .: Stale NFS file handle

Upon bind-mounting an ext4 partition to /var/lib/docker, the problem goes away.

Using Arch Linux with custom-built 3.9.8-1-aufs_friendly kernel.

[rca]

I'm seeing problems with btrfs as well. I don't know if they are specifically in conjunction with AUFS, but building a container to run a Django application will fail with "OSError 28: No space left on device" when Pip attempts to clean up its temp build directory using python's os.remove().

I created /srv/docker on an ext4 filesystem and mounted it with mount -o bind to /var/lib/docker and things work as expected.

[unclejack]

There are a few problems with running docker on BTRFS, but they're not being caused by docker itself or by how docker is using AUFS. The AUFS and BTRFS combo has some problems. Some of these problems are caused by some bits of code which have "TODO"s above or near them, so it's very likely that we're pushing AUFS beyond the point to which it's been pushed elsewhere because we're using it with BTRFS.

These bugs will have to be fixed in AUFS itself, including #1075.

[unclejack]

@rca The issue you're describing is the same as the one I've run into in #1075.

[rca]

Thanks @unclejack; I'll follow up in that issue.

[creack]

See #1075 for followup