Sounds to me it’s more like a legacy artifact, with codepaths which much be tested and maintained, and the decision was made to get rid of it.
It’s interesting as I always considered Kubernetes very enterprise-focused. I wonder what the impact will be in terms of adoption of the new kubernetes version.
Docker's relatively heavy and a pain in the ass to operate. We've switched everything other than our K8s cluster and local Mac dev away from it and I won't be sad if it disappears from either.
Docker, the company, didn't play very nice with the open-source community (ignoring pull requests from certain people, designing docker around just swarm and ignoring other use-cases, etc), so the ecosystem moved on.
10 comments
[ 5.7 ms ] story [ 37.8 ms ] threadMost people I know switched to Podman and Buildah.
> What container runtime is primarily replacing Docker on k8s?
Typically cri-o or containerd depending on the k8s implementation.
It’s interesting as I always considered Kubernetes very enterprise-focused. I wonder what the impact will be in terms of adoption of the new kubernetes version.