This article is based on reporting originally published at ZDNet in October 2019, covering a leaked internal memo from Docker CEO Rob Bearden.
A Leaked Memo Reveals the Funding Crisis
In late September 2019, an internal memo from Docker CEO Rob Bearden was leaked, revealing that the company was actively seeking additional financing. In the memo, Bearden acknowledged the difficult atmosphere inside the company, praising employees for “persevering in spite of the lack of clarity we’ve had these past few weeks” and describing “uncertainty [which] brings with it significant challenges.”
Bearden wrote directly: “We have been engaging with investors to secure more financing to continue to execute on our strategy. We are currently in active negotiations with two investors and are working through final terms. We should be able to provide you a more complete update within the next couple of weeks.”
The message was clear: despite being the company that popularized containerization as a mainstream development practice, Docker Inc. could not sustain itself financially.
The Financial Picture
By the time the memo surfaced, Docker had raised approximately $272.9 million from a roster of notable investors including Benchmark, Coatue Management, Goldman Sachs, Greylock Partners, and ME Cloud Ventures, carrying it through a Series E funding round. Despite that significant capital infusion, the company had never turned a profit.
Docker’s previous CEO, Steve Singh, had promised in May 2019 that the company would be cash-flow positive by the end of that fiscal year. The renewed search for outside capital strongly suggested that target was not going to be met. For venture-capital backers who had supported the company for nearly six years with no IPO in sight, that was a troubling signal.
The Core Business Problem: Monetization Without a Moat
Docker’s financial difficulties were not sudden. They had been building for years and stemmed from a fundamental challenge: the company never found a sustainable way to monetize its enormous mindshare in the container ecosystem.
Docker’s original bet was that Docker Swarm, its container orchestration platform, would become the profit center. That plan collapsed when Kubernetes emerged as the overwhelming community and industry choice for container orchestration. Kubernetes rapidly became the default, leaving little room for competing orchestration solutions. Docker ultimately capitulated and integrated Kubernetes support into its own platform — a pragmatic move, but one that eliminated a potential revenue differentiator.
Docker’s chief product officer Scott Johnston described a revised strategy of layering developer services, CI/CD tooling, content management, and security services on top of Kubernetes clusters — either Docker’s own or third-party ones. While reasonable in theory, the problem was that by 2019 the entire cloud-native ecosystem had converged on Kubernetes. AWS, Google Cloud, Microsoft Azure, Red Hat, and dozens of other vendors were offering similar service layers, many with far greater resources and existing customer relationships.
Open-Source Tensions and Technical Criticism
Docker’s relationship with the open-source community had also become strained. Investor and technologist Ben Kepes put it bluntly on Twitter: “Docker was a victim of its own arrogance and hubris. They thought they could create a walled garden off the back of an OSS project and failed to see there was no obvious way to scale revenue from their model.”
Technical decisions made early in Docker’s architecture also invited criticism. The classic Docker daemon ran as a single large process requiring root access, which created a meaningful security surface area. Red Hat, for example, moved away from Docker in favor of Podman and Buildah — daemonless, rootless tools that aligned better with security-conscious enterprise environments.
Docker did eventually address this. Starting with Docker 19.03, rootless mode became available, allowing Docker to be run without root privileges. However, at the time of the memo, this was still classified as an experimental feature, limiting its immediate adoption in production environments.
What Happened Next
The situation described in the leaked memo foreshadowed significant structural change. In November 2019, Docker sold its enterprise business — including Docker Enterprise and the associated customer contracts — to Mirantis. The remaining company refocused on its developer-facing products, including Docker Desktop and Docker Hub, under the Docker brand.
This split represented a pragmatic acknowledgment that Docker’s value to the market was primarily as a developer tool, not as an enterprise platform competing head-to-head with Kubernetes distributions from Red Hat, VMware, or the major cloud providers.
Lessons for the DevOps Ecosystem
Docker’s business struggles carry useful lessons for anyone building commercial products on top of open-source technology:
- Open-source dominance does not automatically translate to commercial revenue. Docker became synonymous with containers, but awareness and adoption of a free tool don’t pay salaries.
- Picking the wrong platform bet is expensive. Investing heavily in Docker Swarm while Kubernetes gathered community momentum consumed resources that could have funded alternative strategies.
- Architectural decisions have long-term ecosystem consequences. The root-daemon design, while functional, gave competitors a legitimate technical argument for building alternatives.
- Community goodwill is a business asset. Tension with the open-source community made it harder for Docker to attract contributors, enterprise advocates, and downstream integrations.
Docker the technology remains ubiquitous. Docker the business underwent a fundamental restructuring to survive — a cautionary tale about the gap between technical success and commercial viability in the open-source world.