3 ms·
Oh OSTree was definitely around then, but it wasn’t building a competitor to ContainerLinux until rpm-ostree, which made it insanely powerful in that it could b
by SEJeff 9y ago
Oh OSTree was definitely around then, but it wasn’t building a competitor to ContainerLinux until rpm-ostree, which made it insanely powerful in that it could build images from existing (and pervasive) redhat package repos. I’m definitely not arguing that much whatsoever. Only that it wasn’t building a full distro in a way to put it on par with ContainerLinix until after ContainerLinux was a thing and CoreOS was a company.
- emmelaich 9y agoThanks for the info and I agree. Also thank you for your work for Gnome. Awesome! Forgive me for poking around a little more but I like reading computer history. That rpm-ostree first commit was an import from something called pkgsys-ostree. The first commit in pkgsys-ostree was only a little earlier; Aug 2013.
- SEJeff 9y agoHeh, good on you for digging deeper. I think ultimately, the two were developed pretty much independently (Atomic and ContainerLinux), one from ChromeOS, and the other from Fedora / RHEL. They both prove the idea of a small container only os with atomic updates is a solid design to build a container orchestration system (k8s/openshift) ontop of. I'll still stand by the gist of my original comment though in that CoreOS was a thing before Atomic and they had a working P.O.C. before ostree was used to build an entire distro (such as atomic). Either way, we both learned something new so net win.