It's not about current market share but about adoption rates. Which container technology/toolset/ecosystem is more likely to be adopted by the average software shop today?
It's the wrong question unless you are in the business of profiting off of container tech directly. What are you doing for the stakeholders delegating your pay checks and the person authorized to fire you? If they are happy, then it doesn't matter what the company uses. Most transactions and the world's wealth are stored and processed on operating systems and frameworks most people have never heard of which will outlast either of these by decades but that doesn't mean you should or shouldn't use them necessarily..
I'm well aware that there's tons of time proven software that serves us well and will continue to do so for some decades. Yes, most of this is not written in the PL/framework combo du jour, true. You seem to think I want everyone to switch to Docker/Kubernetes. I don't.
Fair enough, and the parent topic about /switching/ between broadly similar technology like operating systems is where departments usually go awry. My axe to grind is about initial selection when starting from scratch (do you really need fad tech? Statistically, likely not), or playing nicely in an existing environment and being very careful with new tech (can the company internalize and support fad tech? Statistically, likely not)
OP asked what stops people from switching to BSD. I agreed that for me, too, the missing Docker toolchain/runtime is a dealbreaker for me, as I have to work with these technologies on a daily basis. As Docker and friends see rapid adoption, others will think twice whether they switch to a BSD and have to run a Linux VM, too. I'm not sure what you're after here. You seem to think that Docker and Kubernetes are "fad technology" and are inferior to some alternative? Which orchestrator would you recommend? Which container tech?
Again it's not a judgement against the technology. What I'm getting at is the talking that fad technologies won the industry is false and too early to call like that; in the particular company you are working in docker and kube you may have to use. In industrial terms, they are far from required and are not used in the majority of deployments. Proprietary schedulers or other deployment machinery are running most workloads. Distant second by cluster size is Mesos, which has passed its fad phase.
I am currently using Nomad which works on multiple platforms and that is a requirement for my particular setting. I don't currently use containers in production environments and only see negatives to introducing them into this particular setting. This is not general advice to use nomad, just a counterpoint to any particular fad tech being an industrial requirement.
