4 ms·
Source: the libcontainer release announcement: https://blog.docker.com/2014/03/docker-0-9-introducing-execution-drivers-and-libcontainer/ https://blog.docker.co
by SEJeff 11y ago
Source: the libcontainer release announcement: https://blog.docker.com/2014/03/docker-0-9-introducing-execution-drivers-and-libcontainer/ https://blog.docker.com/2014/03/docker-0-9-introducing-execu...
"""
Thanks to libcontainer, Docker out of the box can now manipulate namespaces, control groups, capabilities, apparmor profiles, network interfaces and firewalling rules – all in a consistent and predictable way, and without depending on LXC or any other userland package. This drastically reduces the number of moving parts, and insulates Docker from the side-effects introduced across versions and distributions of LXC. In fact, libcontainer delivered such a boost to stability that we decided to make it the default.
"""
- tribaal 11y agoThanks, but that's still not saying what was flaky. In fact it doesn't point out any problems with LXC at all except a general hand-wavy statement about stability (which sounds a lot like NIH-justification). I was looking for actual problems - since I've never encountered any with LXC/Docker, I'd be interested.
- SEJeff 11y agoJust relaying what I heard from upstream, sorry but you'd have to ask them to details.