libnetwork

There's nothing about Go that makes it particularly good for containers. It actually requires some ugly hacks in C to make it handle namespaces correctly (because namespaces are configured per-thread, and Go decides to spawn new threads somewhat arbitrarily which is not visible to the program). https://github.com/docker/libnetwork/issues/1113 https://github.com/docker/libcontainer/tree/master/nsenter https://www.weave.works/blog/linux-namespaces-and-go-don-t-m... EDIT: TIL this is fixed in Go 1.10 which came out in February: https://golang.org/doc/go1.10#runtime If rust continues to improve ergonomics and library support, I don't see anything stopping it from replacing C except in niche embedded systems that don't get LLVM support.

Could it be that the teams are simply focused on adding K8s support and getting the Docker EE out of Beta? Public statement on their blog after the K8s announcement in EU: "But it’s equally important for us to note that Swarm orchestration is not going away. Swarm forms an integral cluster management component of the Docker EE platform; in addition, Swarm will operate side-by-side with Kubernetes in a Docker EE cluster, allowing customers to select, based on their needs, the most suitable orchestration tool at application deployment time." https://blog.docker.com/2017/11/swarm-orchestration-in-docke... There's still plenty of PR's and activity in the SwarmKit and Libnetwork repos: https://github.com/docker/swarmkit/pulse/monthly https://github.com/docker/libnetwork/pulse/monthly