My feeds this week are wall-to-wall Docker, and for once it's not a security advisory. At DockerCon in Austin they announced two things that landed at the same time and got tangled together in everyone's head: the Moby Project, and a rebrand of the product into Docker CE and Docker EE. The reaction has been somewhere between "sensible" and "what on earth is going on", depending on who you follow, and I've spent a couple of evenings trying to work out which camp I'm in.
So here's my read, having let it settle for a few days.
what actually changed
The thing people keep conflating is the open-source project versus the product you download. Up to now "Docker" meant both, which was fine until it wasn't. Moby is the new home for the upstream, open-source components: the runtime bits, the assembly toolkit, the libraries. The idea is that Moby is the factory, and Docker the product is one thing that rolls off the line, built from those components but not the only possible thing you could build.
Alongside that, the product itself splits in two. Docker CE, Community Edition, is the free one most of us run. Docker EE, Enterprise Edition, is the supported, certified, paid one with the lifecycle guarantees a large org wants. The version numbers move to a date-based scheme too, so you'll start seeing things like 17.03 instead of 1.13, year-dot-month.
None of that is unreasonable on its own. The bit that caused the noise was the surprise. The repository many people had bookmarked got renamed to moby/moby more or less overnight, links broke, and a lot of contributors found out the structure of the thing they'd been committing to had changed by reading the news. That's a process failure, not a technical one, but it set the tone for the week.
why a company would do this
Strip away the branding and the motivation is straightforward, and I've some sympathy for it. Docker the company needs to make money, and the obvious lever is an enterprise edition with support contracts. To sell that with a straight face you need a clean line between "the free community thing" and "the thing we'll put an SLA on". The CE/EE split draws that line.
Moby does something subtler. It lets the company keep developing in the open while making it clear that the upstream project and the shipped product are not the same promise. If you're a vendor who wants to assemble your own container system from the same parts, Moby is meant to be your starting point. It's the same move plenty of projects have made: a community upstream that the commercial product is downstream of. Sensible, if you ignore how it was rolled out.
The cynical reading, which I half hold, is that this also conveniently muddies the "is Docker open source" conversation. The product you actually run becomes a thing built on top of an open project rather than the open project itself. Whether that matters to you depends entirely on whether you were ever going to fork it, and almost nobody was.
what it means for the likes of me
Honestly, for day-to-day use, very little changes this week. I'll carry on running the community edition on the homelab and at work, the commands are identical, my Compose files don't care. The version string looks different and that's about the size of the immediate impact.
The longer game is worth watching, though. The interesting question is whether Moby actually attracts the ecosystem it's designed for, other people building real systems out of the components, or whether it just becomes "the place Docker develops Docker" with a different name on the door. The first outcome is genuinely good for everyone. The second is a rebrand with extra steps.
There's also the runtime layer underneath all this, which is the part I think will matter more in a year than the branding does. containerd and runc keep getting more clearly separated out as reusable pieces, and that standardisation is the quiet, important work. If the lasting result of this week is that the core container runtime becomes a boring, shared, swappable component that nobody owns the brand of, that's a better outcome than any logo.
the bit I keep coming back to
The technical decisions here are mostly fine. The way they were communicated is the lesson. A pile of people gave their evenings and weekends to a project, and the structure of that project changed underneath them with very little warning, dressed up as a launch. You can do the right reorganisation and still bruise the community that got you there, just by doing it as a surprise instead of a conversation.
So I'm cautiously fine with the substance and a bit wary of the style. I'll keep running the community edition, keep half an eye on whether Moby grows into its ambitions, and keep being grateful that the actual containers on my actual servers neither know nor care what the marketing is called this quarter. As ever, the software does its job regardless of what's printed on the box.