4 ms·
"Why would that be the case?" One argument could be that their moat is mostly brand. And, increasingly, other brands are working around them. Like Kubernetes
by tyingq 8y ago
"Why would that be the case?"
One argument could be that their moat is mostly brand. And, increasingly, other brands are working around them. Like Kubernetes. They already offer non-docker runtimes. They could, at some point, offer and promote their own packaging tool too. People might use a K8S tool solely because it's the "default setting".
- Aeolun 8y agoI have a ton of docker images already that work perfectly fine. Why would I switch to something else?
- ATsch 8y agoThese container images will continue to work.
- johannes1234321 8y agoThere will be more created in the future, than was in the past.
- fatherlinnux 8y agoThe OCI standards make it so that it doesn't matter if you switch or not. Your images will work anywhere with any tool (aka Cloud Providers, Kubernetes, Podman, Buildah, etc.) Everybody has OCI compliant tools, even Docker - Docker founded the OCI.
- Aeolun 8y agoSame point though. If docker works, why switch to anything else?
- tyingq 8y ago"The Kubernetes project is excited to announce kocker, a new docker compatible image management tool. Kocker will support features you've been asking for, like non-priv-by-default containers, enhanced performance in k8s..." Made up, but I imagine something like that.
- zaro 8y agoThat's podman you are describing an it alrwady exists.