3 ms·

I don't see the point of ostree personally. It's overly complicated for what it's trying to do (immutable base). I have been working on an immutable OS that u

I don't see the point of ostree personally. It's overly complicated for what it's trying to do (immutable base). I have been working on an immutable OS that uses squashfs instead and it seems to work better. The contract is tighter with squashfs, as you really _can't_ change the underlying squashfs stuff. Upgrades are easily scriptable and transparent on what they're trying to accomplish, too. The distribution is designed as a "meta" distribution with different flavors (deb, ubu, arc, fed, etc) that you can easily "swap" to just by changing the boot stuff, all configured to deliver the same kind of functionality (container host, mostly).

PlutoIsAPlanet 3y ago
OSTree is moving to using OCI images, which removes a large amount of complexity in its current form. On top of using composefs, this will make it impossible to change the underlying files manually without causing the file to be invalidated. https://fedoraproject.org/wiki/Changes/OstreeNativeContainerStable https://fedoraproject.org/wiki/Changes/OstreeNativeContainer...
- vaylian 3y ago
  Does that mean that system updates will pull complete container images instead of diff?
  - dralley 3y ago
    I believe diff support between container images is being worked on as well. edit: there's a link in that document to https://github.com/containers/image/pull/902 https://github.com/containers/image/pull/902
merb 3y ago
Yeah I do not like it as well. Especially since redhat tried to force it on users of CoreOS Container Linux, with a completely new os without any upgrade path and half the features. Forking base worked at the beginning , but was painful and broke sometimes. I migrated all coreos machines to flatcarlinux which was a fork of coreos and was bought by Microsoft and is still maintained by them. What a strange world. (I was a big fan of back than and used centos/fedora heavily. I dropped everything in favor of Debian/tumbleweed/manjora and almalinux(centos migrated)) I think flatcar uses squashfs

PlutoIsAPlanet 3y ago

OSTree is moving to using OCI images, which removes a large amount of complexity in its current form. On top of using composefs, this will make it impossible to change the underlying files manually without causing the file to be invalidated. https://fedoraproject.org/wiki/Changes/OstreeNativeContainerStable https://fedoraproject.org/wiki/Changes/OstreeNativeContainer...

vaylian 3y ago
Does that mean that system updates will pull complete container images instead of diff?
- dralley 3y ago
  I believe diff support between container images is being worked on as well. edit: there's a link in that document to https://github.com/containers/image/pull/902 https://github.com/containers/image/pull/902

merb 3y ago

Yeah I do not like it as well. Especially since redhat tried to force it on users of CoreOS Container Linux, with a completely new os without any upgrade path and half the features. Forking base worked at the beginning , but was painful and broke sometimes. I migrated all coreos machines to flatcarlinux which was a fork of coreos and was bought by Microsoft and is still maintained by them. What a strange world. (I was a big fan of back than and used centos/fedora heavily. I dropped everything in favor of Debian/tumbleweed/manjora and almalinux(centos migrated)) I think flatcar uses squashfs