Understanding Docker’s Rebranding to Moby and the Role of LinuxKit

DockerCon 2017 highlighted the launch of the Moby project, a rebranding of the original Docker open‑source repository that caused significant debate within the Chinese container community, with some contributors declaring that “the community will never have Docker again.”

The rename was performed without prior notice, transferring the Docker organization’s code to a new GitHub organization called Moby, prompting criticism that Docker aimed to shift its extensive search‑engine footprint and fan base to its commercial products.

Analysis of the move suggests that Docker’s strategy was to consolidate the brand value of the “Docker” keyword under the company, leveraging the project’s popularity to promote Docker‑CE and Docker‑EE, while limiting third‑party use of the name.

“From now on, the value of the Docker keyword belongs only to Docker Inc.”

The article also examines the importance of three key channels for open‑source project success—Google search results, Stack Overflow Q&A, and Google Group discussions—and how Docker’s dominance in these areas contributed to its ecosystem’s growth.

Beyond the rename, the piece introduces LinuxKit, a project under the Moby organization that builds lightweight, custom OS images (kernel, disk, BIOS) for running containers in non‑Linux environments, effectively acting as a Unikernel‑style distro.

LinuxKit’s primary use cases include creating portable OS images for cloud providers (e.g., GCE) and simplifying container deployment on Windows or macOS via a minimal VM, though it still relies on virtualization.

The article concludes that while Docker’s rebranding caused confusion, the Moby project and LinuxKit will continue to play vital roles in the container stack, and most users can remain focused on higher‑level orchestration tools such as Kubernetes, SwarmKit, or DC/OS.