Every year at DockerCon, there would be flashy announcements that went nowhere. As a developer, those years from 2013 to 2017 were both super exciting and super frustrating. Everything started falling apart when Docker (the project) got split into Moby for open source and the rest went commercial. Docker started to sell Docker Swarm (the original), only to kill it a year later with a new Docker Swarm (what we have today). Then, Kubernetes started growing traction, leapfrogging both Docker Swarms, Mesos, and others in adoption. They never had a cohesive commercial plan. Just lots of empty promises and burned bridges.
When I think of Docker (the company), I feel bitter about all the projects they killed in their attempt to own the market. I love using Docker (the software), but the company's just one big disappointment.
I don't think you have Docker without VC money. I think at best you have some LXC-lite project that is intertwined with GCP/AWS/Azure but unfortunately, I don't think you get something as quite polished as Docker in the same timeframe without VCs pouring millions to hire people to work on it.
Where I am sympathetic to Docker is Docker wouldn't have worked as your standard Open Source project; it took a ton of paid engineering hours (and you can argue X% was wasted on projects that went nowhere, but that's a given in any org), to get the software and infrastructure right, and if they had tried to charge developers they would have gotten nowhere. Even now, where people are keenly aware of the value of Docker, trying to monetize it is met with tears and angry blog posts.
I think Swarm was the plan (as the money has always been in providing infrastructure), Google just had more developer sway (which also killed Mesos).
The way I see it are there probably a ton of services you could build with the right team and right amount of people that could make an even greater impact than Docker on productivity and they would never be built because it would be way too difficult to monetize and the people with the talent to build it are going to get paid more working at FAANG to do any sort of OSS approach.
There's a big difference between creating value and capturing value. Probably thr biggest single issue with capitalism in general.
They were always in a race to reinvent everything the Docker way. Which is, sort of, what you need to do if you want to become an enterprise software company, if that's where you think the money is. It's pretty much exactly in the footsteps of VMware. But to make that work, they would have had to work much closer to Windows, which probably was even harder than the Linux community.
Docker couldn't have existed without VC money. Free hosting was what made them hugely popular. Docker was a VC productization of containers.
But they weren’t paying back fast enough, and K8s was making waves. Better make money fast while you can. Time for the squeeze play so the VCs can win.
If they had been allowed to grow at a more natural rate maybe it would all be fine. If they were allowed to be happy with a 40% share of a big future market, things could be great.
But that’s not the VC-shoot-for-the-moon way.
"Docker is also a company, and companies are expected to produce revenue." That reads like wages, office rent and perhaps a boat for the founders. But they can't be that humble anymore, not after burning through a quarter billion in VC money. (even if those numbers seems surprisingly harmless compared to some more consumer oriented VC bonfires)
Now it's their job to make those investments winning bets or ruin the company trying. All that free image CDN convenience much of the docker revolution was built on? Too good to be true, effectively a loan from VC betting on getting people hooked.
> be the cashcow that turned
> that into cashflow. And then
> k8s happened.
We are still using Docker Swarm in production. It seems to be working fine so I always wondered why it never took off. But I am not a Devop. Can sb please give some insight on why kubernetes took off instead and why Dock Inc. failed with its cloud product?
On the other hand, Dock Inc. failed with its cloud product because it was not able to compete with other cloud providers like Amazon Web Services (AWS), Microsoft Azure, and Google Cloud Platform. Dock Inc. was a startup that was focused on providing a container-based platform for building and deploying applications. However, it was not able to gain traction in the market, and its product was not as mature or feature-rich as those offered by larger cloud providers.
Another reason for Dock Inc.'s failure could be a lack of community support. Kubernetes has a strong community of developers who contribute to the project and help improve it. This has helped to build a robust ecosystem of tools and services around Kubernetes, which has made it easier for developers to adopt it. Dock Inc. may not have had the same level of community support, which could have made it harder for them to gain traction in the market.
There are quite a few optional tools built on the k8s model, like service meshes or tools to orchestrate a postgres cluster.
Swarm is a small piece of that, the scheduling system, and you have to run it yourself. It's really not comparable.
IMHO, Google did something smart/evil here. Google did not use the docker-compose style yaml files for k8s configurations. This turned into a big deal. If you have a docker-compose file and want to run it in k8s - you cannot. So you need to make a decision: go with docker-compose yamls which has no place to be hosted except swarm OR go with k8s yaml style and be able to run it on aws,gcp, etc.
I rather have to deal with WebSphere 6.1 yet again, than a poorer replication of its developer experience with lesser tooling.
I could see that I was being too abstract, so I distilled it -- and I more or less begged him to not take any more money. (Sadly, Silicon Valley's superlative, must-watch "Sand Hill Shuffle" episode would not air until 2015, or I would have pointed him to it.) When they took the $40M round -- which was an absolutely outrageous amount of capital to take into a company that didn't even have a conception of what they would possibly sell -- the future was clear to me.
I wasn't at all surprised when the SVP washouts from the likes of VMware and IBM landed at Docker -- though still somehow disappointed when they behaved predictably, accelerating the demise of the company. May Docker, Inc. at least become a business school case study to warn future generations of an avoidable fate!
- Bryan Cantrill, https://news.ycombinator.com/item?id=28460504
They've raised a tonne of capital, and it probably looked sane at the time. And now they're grasping at straws trying to figure out how else they can turn this into revenue.
A lot of the recent narrative has been worded like pivoting into a glorified webhost was their evil plan all along. It's not, it's an act of desperation.