Docker was on every lips a couple years ago. Every small and medium company adopted it or was about to.

What’s left of Docker 3-5 years later? Well, not much.

Let’s rephrase the question to be more accurate. What company still cares about docker? Surprisingly the answer is nil.

The world has moved on.

Docker job prospects?

If you’re (only) a docker expert, you’re in troubles right now. There are no more jobs looking for docker expertise and you’re dangerously close to unemployable.

Docker expert meaning intimately familiar with containerization concepts and docker-specific implementations, as well as having experience building, running and debugging containers in production.

Some typical interview questions to expect (in 2017):

• What is docker?
• What is a container?
• What’s the difference between a VM and a container?
• What’s the good practice to build a docker images?
• How to build a container?
• Where are images stored?
• What are cgroups?
• Can you name some docker commands?

Here’s 6 typical questions being asked instead (in 2019):

• What is a pod?
• What is a deployment?
• What is a stateful set?
• How to update an application without downtime?
• What is a namespace? When to use it?
• Can you name some kubernetes commands?

The top questions are a piece of cake but all the Docker expertise in the world couldn’t help to answer the bottom ones. Those are kubernetes concepts, a whole new world of learning. Have a read, better keep up with current technologies to stay employable.

Companies are strongly biased toward kubernetes as of late. They’re really looking for the unicorn with kubernetes experience, preferably years, in production.

Kubernetes

Kubernetes has changed the landscape almost overnight. In the process, it also revamped every term around containerization and orchestration (see the questions above for some examples).

What was once called docker is now only referred to as a “container engine”. This neat marketing trick has been an outstanding success. Like an engine running a car, the container engine is still there, in fact it is running absolutely everywhere, including alongside kubernetes as a dependency, but its presence is ignored and has been forgotten by all.

Walk into a meeting, a job interview, a conference… kubernetes is omnipresent but the container engine never comes up anymore.

That’s the visible part of the iceberg right there. Kubernetes is integrating the whole ecosystem vertically and becoming the go-to solution.

Behind the scenes, it’s a subtle move repositioning Docker as a replaceable engine, waiting to be pushed out. There are multiple actors at play incentivized and actively working to take it out (RedHat, Google, Amazon, etc…).

Kubernetes has seduced management

Kubernetes has succeeded where docker failed. Management buy-in.

Working in and around F500. Pay attention to top management meetings, all-hands, announcements and other large corporate events. That’s pointing to where the time and the money is going to, paving the road to the future.

Well, half the time it’s paving the future, the other half is getting budget and paving self-promotion. Either way, that’s the right road.

Some of the strong recurring themes are #Cloud #Kubernetes #AWS #AI #MachineLearning #BigData #BlockChain. (Take a guess which one is a game changer and which one is a fad)

Counting how often kubernetes is mentioned, it is almost on every event, repeated many many times over. Whereas the container engine has been mentioned exactly zero times since the beginning of the year. (Still on the lookout for it, there’s 2 months left in the year.)

F50 are heavily invested or investing in kubernetes. More headcount, open hiring, consulting business, 6 and 7 figures checks going to enterprise providers and contracting agency. Not a penny of it is going to Docker.

It’s glaring obvious at this stage that docker has utterly failed to capitalize in the enterprise.

Where’s the money going?

First and foremost, “DevOps” people, whether that’s full time employees or contractors or consultants. Remember that human resources are always driving the project and the costs, unlike software license or hardware. Short parenthesis for workers, lots of opportunities in contracting / consulting. Obviously the market is especially hot for ex-googlers or other who contributed to these technologies.

For smaller and medium companies, usually on the cloud. The big money is flowing to AWS EKS, AWS ECS, Google GKE or Microsoft Azure.

For medium and large companies, on-premise or hybrid. The big money is flowing to VmWare (VM are still strong), Pivotal Cloud Foundry and RedHat OpenShift.

For enterprise consulting, the big dog seems to be Heptio, just bought by VMWare for $400M (a wise acquisition). On a side note, it shouldn’t take long before VmWare rolls a fully-managed kubernetes solution out-of-the-box on top of vCenter.

Kubernetes needs a container registry as well. Managed-solutions in the cloud have their own registry included, another line item in the billing.

On premise, either it’s the free registry, or a commercial solution when money is on the table, Quay seemed to be the dominant one for some time. The registry market might be a bit saturated lately though because everything jumped-on to be a registry including gitlab, github, nexus and artifactory.

The container engine registry is available in a commercial edition. Strangely enough never found it in any company or meet anybody using it. Really wondering if it has any customer or revenues. This might be one of the biggest commercial failure, right on the level of Apple map.

podman says hello

Since all the bits are available separately through different solutions, more or less managed. The only thing left to replace is the container engine itself.

Say no more. Challenge accepted! RedHat is killing it from RHEL 8 onward, transparently replacing it with its own engine. The name is podman.

Is it possible to kill a command? or more than that, a brand? or more than that, a vendor? Just like that?

Yes, it is. It’s been done multiple times in recent history. One of the most notable examples is mysql. MySql was acquired by Oracle somewhen around 2010 and subsequently dropped and killed by the community. The fork is called MariaDB. If you’ve run a “apt-get install mysql” in the past decade, high chances it setup MariaDB instead, getting aliased and substituted transparently.

Long story short. It’s a walk in the park for RedHat to do the same with “docker” => “podman“.

Who’s gonna buy Moby?

Totally $272M in funding over 9 rounds. The sell price would have to be quite high for investor to make a return.

That being said. Don’t fall into a common mistake of thinking that companies fail and become worthless. An unsuccessful not-growing company by Silicon Valley standards is still a very respectable medium business. A regular business could be worth $100M with a few hundreds employees. Talent acquisitions or killer acquisitions can do $1M per head.

Current headcount shows the company in the 100-250 range. No matter what metrics is considered, the company ain’t worth multiples of what it raised.

The worse may have yet to come though. The trend may be going downward rather than upward and I’m sorry for employees reading this. Employees are leaving, they can see the tide turning through the bad press and the better opportunities elsewhere.

The only thing of value might be the public image registry. Personal data and contacts from all members and organizations registered (sales lead or other monetization). Plus a direct automated deployment pipeline to almost every company in the world (the potential for dark patterns and malware is endless). Recall SourceForge sold for $20M in 2012 to distribute adware.

All things included, there’s some value to recoup. Just closer to 8 figures than to 10.

Even if there was a buyer, assuming one of the usual suspects, RedHat/Pivotal/VMWare/AWS/Google/Microsoft. Why buy something today when it will go for half tomorrow? Why buy something when you already sell substitutes products/services better positioned? There is no pressure for anybody to acquire really.