This is a transcript of a keynote I just gave at Dockercon. But the keynote had in-depth demos and the blog post doesn't. It will make more sense with the demos

This is a transcript of a keynote I just gave at Dockercon. But the keynote had in-depth demos and the blog post doesn't. It will make more sense with the demos. I will try to summarize: when we build Docker for Mac, Docker for Windows, Docker for AWS etc, we assemble a lot of individual components into a complete platform. Then we pack that platform into a bootable artifact for the target environment. That's a lot of work, and it gets harder as the number of targets multiply. We developed a framework to make this more efficient. That framework has become the de-facto upstream of the Docker platform - it sits between the individual upstream projects and the finished product. So we're open-sourcing it as Moby, moving all of our open-source process under it, and inviting the community to come play. Think of it as the "Fedora of Docker". Here's more technical details from the readme: https://github.com/moby/moby/blob/moby/README.md https://github.com/moby/moby/blob/moby/README.md TLDR: - If you're a Docker user, nothing changes: Docker remains the same - If you're a Docker open-source contributor, you're now a Moby contributor. Everything is basically the same, except more modular and more open, and you are less tied to Docker. - If you're building non-Docker container platforms, it's easier to share components and ideas with the Docker community, without being forced into anything you don't like. The Moby tooling itself is pretty neat: you define all the components in your system (including the OS and hypervisor, if required), then pack them into the artifact of your choice. For example you can assemble LinuxKit+ContainerD+Redis into a tiny "RedisOS", and then boot it straight from bare metal; or virtualize it with HyperKit and run it on a Mac; or virtualize it with HyperV and run it on Windows. Moby does all of this for you automatically (this is one of the keynote demos). We also showed a "Kubernetes in a box" assembly, to show that you don't have to stick to Docker-built components.