News for hackers. Stuff that matters.
Re:Docker 1.11: The first OCI-compliant runtime, built on co... by sams99 on Wednesday April 13, 2016 @08:52PM (#11493574)
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.

Re:Docker 1.11: The first OCI-compliant runtime, built on co... by cpuguy83 on Wednesday April 13, 2016 @09:04PM (#11493622)
Sounds likely to be 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.

Re:Docker 1.11: The first OCI-compliant runtime, built on co... by rodionos on Thursday April 14, 2016 @03:18AM (#11494848)
We hit 18180 in all our images with Java applications. Workaround was to upgrade the kernel.
Re:Docker 1.11: The first OCI-compliant runtime, built on co... by sams99 on Wednesday April 13, 2016 @09:10PM (#11493642)
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.
Re:Docker 1.11: The first OCI-compliant runtime, built on co... by facorreia on Thursday April 14, 2016 @10:17AM (#11496898)
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.