I'm very suspicious of their benchmarks - all of the tests they list are largely network-bound (including build, as the Dockerfile they are presumably using to do the build is mostly apt-get/wget instructions), and there's zero discussion of how they eliminated network variance. Using docker pull/wget/etc to benchmark a filesystem gives me very little faith that they really understand what they're doing.<p>Furthermore the install script is troubling: "sudo curl ... | bash" -- in this curl runs as root, but bash runs as the user, which is definitely not what you want to do. Either they should both run as the user, or curl should run as the user and bash as root. But not this.<p>The setup script also looks like it wants to nuke /var/lib/docker, which may be an unpleasant surprise to people wanting to try this.<p>Honestly, the more I look at this, the more I can't help but shake the feeling that this really isn't everything it claims to be.
This combines the advantages of Device Mapper (granularity) and AUFS/overlay (page cache re-use), and doesn't require new kernel code. Promising!
A docker graph-driver that deals with layers as first class citizens - what a great idea! Hopefully this will make my docker builds quicker :-)<p>This quote from the Readme stands out:<p>> The LCFS filesystem operates directly on top of block devices, as opposed to over two filesystems that are then merged.