4 ms·

This is a huge upgrade that is super welcome. Recently (on 1.9) we have seen quite a few cases where we had "zombie" containers, these are container that can n

by sams99 10y ago

This is a huge upgrade that is super welcome. Recently (on 1.9) we have seen quite a few cases where we had "zombie" containers, these are container that can no longer be started or stopped due to cgroup misconfiguration or something along those lines. The new architecture means that for weird cases like this all we need to do is kill off runc without forcing every container on the box to restart (by restarting the docker service which is what we do now). It is also really nice that you can now launch apps on runc direct without needing a docker intermediary.

cpuguy83 10y ago
Sounds likely to be https://github.com/docker/docker/issues/18180 https://github.com/docker/docker/issues/18180 If so, it's a bug with a particular (newer) version of AUFS that has been fixed in most distros.
- sams99 10y ago
  most likely that bug, been tracking it, but I think this goes beyond this specific issue. It makes docker a lot more robust when bugs like this pop up in future.
- rodionos 10y ago
  We hit 18180 in all our images with Java applications. Workaround was to upgrade the kernel.
facorreia 10y ago
I particularly like that in addition to refactoring the architecture, they worked on stabilization. > With the containerd integration comes an impressive cleanup of the Docker codebase and a number of historical bugs being fixed. In general, splitting Docker up into focused independent tools mean more focused maintainers, and ultimately better quality software.