Overlayfs like aufs is a layered filesystem but overlayfs got merged into the kernel. Aufs inpsite of a lot of effort was not merged. Before merge the module wa

Overlayfs like aufs is a layered filesystem but overlayfs got merged into the kernel. Aufs inpsite of a lot of effort was not merged. Before merge the module was overlayfs, after merge it was renamed to overlay. I think its the responsibility of Docker users to understand the technologies they are using. Docker has got into the bad habit of wrapping open source Linux technologies and promoting them in a way that makes it feel like Docker invented it. They did it to LXC and they are doing it to aufs and overlayfs. The HN community is far too vested in Docker to offer any real scrutiny and is very much a part of this hijack. What is a Docker overlayfs driver? How is simply mounting a ready made overlayfs filesytem already present in the kernel or aufs a driver? These terms not only mislead but prevent recognition of the work of the authors of overlayfs and aufs. They also require scrutiny as layered filesystems have tons of issues and the only way these can be resolved is engaging with the developers who most dockers users don't even know about. Docker can't solve these issues only work around them.