News for hackers. Stuff that matters.
Re:Roadmap for CoreOS Integration with Red Hat OpenShift by zapita on Wednesday May 09, 2018 @08:06PM (#17035414)
Your answer is 99% techno-marketing bullshit, but you still delivered the kernel of a credible explanation: systemd.

It makes perfect sense now. cri-o, being "daemonless", reinforces the central role of systemd in orchestrating system resources, whereas containerd, being a daemon, weakens it. I can see how Red Hat architects would not love the idea, given the importance of systemd in the RHEL/Openshift stack.

Thanks for enlightening me, if only accidentally.

Re:Roadmap for CoreOS Integration with Red Hat OpenShift by davidmr on Wednesday May 09, 2018 @10:00PM (#17035898)
There’s no call to be so rude. The RH/CoreOS people here are acting in good faith, I think they’re being exceptionally helpful, and they don’t even need to be answering questions at all.