And a quick run through the previous article[0]: > Docker Issue: Breaking changes and regressions Yes, it's new, and it changes regularly. This is why you do

And a quick run through the previous article[0]: > Docker Issue: Breaking changes and regressions Yes, it's new, and it changes regularly. This is why you do what you do with any other piece of software in an enterprise environment: Pick a stable release (e.g. 1.7), deploy it, then upgrade your development environment to the next stable release (e.g. 1.11) and work through the breaking changes. Regressions are frustrating, I'll agree, but it's free software: report the regressions and help the community fix them. > Docker Issue: Can’t clean old images A built-in feature to do so was added in 1.13 (a few months after this article was published). > The only way to clean space is to run this hack, preferably in cron every day: docker images -q -a | xargs --no-run-if-empty docker rmi That's not a hack, that's how you do things in Unix. > As a long-standing goal, the AUFS filesystem was finally dropped in kernel version 4. > There is no unofficial patch to support it, there is no optional module, there is no backport whatsoever, nothing. AUFS is entirely gone. While the first point is technically true (actually, based on some light googling, I'm not sure it was ever merged in the first place), many distributions provide it as an optional kernel module. For example, Ubuntu provides it in linux-image-extra. Yes, Virginia, you can build kernel modules from source. > How does docker work without AUFS then? Well, it doesn’t. It does: Btrfs, Device Mapper, ZFS... > So, the docker guys wrote a new filesystem, called overlay. [..] Note that it’s not backported to existing distributions. Docker never cared about [backward] compatibility. Docker supports multiple storage drivers, one benefit of which is to be able to support older systems: AUFS on older distributions, OverlayFS on newer. The container abstraction allows you to not care about the underlying storage subsystem. > Right now. We don’t know of ANY combination that is stable In November 2016? Are you kidding? 0. https://thehftguy.com/2016/11/01/docker-in-production-an-history-of-failure/ https://thehftguy.com/2016/11/01/docker-in-production-an-his...