4 ms·

The k8s community is moving full steam ahead toward replacing docker containers with OCI-compliant cri-o/podman. Docker had a good run with a great idea, but i

The k8s community is moving full steam ahead toward replacing docker containers with OCI-compliant cri-o/podman. Docker had a good run with a great idea, but it doesn’t make sense to leave all of this vendor-agnostic tooling reliant on Docker (the company).

radus 8y ago
What about a docker-compose alternative?
- mbell 8y ago
  https://github.com/kubernetes/kompose https://github.com/kubernetes/kompose or https://github.com/helm/helm https://github.com/helm/helm or keep using docker's dev client, it can target a locally running k8s now.
rattray 8y ago
Interesting, where can we learn more about this? (eg; cri-o, podman, I saw rkt mentioned elsewhere)
- dan_quixote 8y ago
  This is a post explaining how the k8s community got to the current state: https://medium.com/cri-o/container-runtimes-clarity-342b62172dc3 https://medium.com/cri-o/container-runtimes-clarity-342b6217... And here’s a little info on why we’re using cri-o at SUSE: https://www.suse.com/c/cri-o-container-runtime-on-suse-caas-platform-3/ https://www.suse.com/c/cri-o-container-runtime-on-suse-caas-...
  - rattray 8y ago
    cool, thanks!
- bacongobbler 8y ago
  hit up SIG-Architecture. https://github.com/kubernetes/community/tree/master/sig-architecture https://github.com/kubernetes/community/tree/master/sig-arch...
- rwmj 8y ago
  I've been reading Dan Walsh's blog about podman & cri-o: https://medium.com/@rhatdan https://medium.com/@rhatdan (Disclaimer, I work in the same company, but not in the same department/group)
raesene9 8y ago
I don't think that all the k8s distros are looking at cri-o, I think that many are considering cri-containerd instead, which kind of makes sense as they're all using containerd, so whether you need a whole separate program to manage that interface is debatable.

4 ms·

The k8s community is moving full steam ahead toward replacing docker containers with OCI-compliant cri-o/podman. Docker had a good run with a great idea, but i

by dan_quixote 8y ago

radus 8y ago
What about a docker-compose alternative?
- mbell 8y ago
  https://github.com/kubernetes/kompose https://github.com/kubernetes/kompose or https://github.com/helm/helm https://github.com/helm/helm or keep using docker's dev client, it can target a locally running k8s now.
rattray 8y ago
Interesting, where can we learn more about this? (eg; cri-o, podman, I saw rkt mentioned elsewhere)
- dan_quixote 8y ago
  This is a post explaining how the k8s community got to the current state: https://medium.com/cri-o/container-runtimes-clarity-342b62172dc3 https://medium.com/cri-o/container-runtimes-clarity-342b6217... And here’s a little info on why we’re using cri-o at SUSE: https://www.suse.com/c/cri-o-container-runtime-on-suse-caas-platform-3/ https://www.suse.com/c/cri-o-container-runtime-on-suse-caas-...
  - rattray 8y ago
    cool, thanks!
- bacongobbler 8y ago
  hit up SIG-Architecture. https://github.com/kubernetes/community/tree/master/sig-architecture https://github.com/kubernetes/community/tree/master/sig-arch...
- rwmj 8y ago
  I've been reading Dan Walsh's blog about podman & cri-o: https://medium.com/@rhatdan https://medium.com/@rhatdan (Disclaimer, I work in the same company, but not in the same department/group)
raesene9 8y ago
I don't think that all the k8s distros are looking at cri-o, I think that many are considering cri-containerd instead, which kind of makes sense as they're all using containerd, so whether you need a whole separate program to manage that interface is debatable.