I don’t really understand how ostree works from a use standpoint. What I am looking to do is create a custom immutable Linux where I make a filesystem image and then devices can pull the image if I make changes upstream I’m looking for a way to update a local image.
So basically I’m wanting to create some sort of OStree repo. I know rpm-ostree exists but I want something that is more distro agnostic. (I want to use Debian and maybe gentoo as the base)
There is no such thing as “distro agnostic” when you’re describing the thing that makes a distribution what it is. That’s like saying “I’m trying to make a package manager that integrates with all other package managers”.
Why would you do that when they already have working package managers?
What you’re actually describing in sharing layers and state changes is not possible the way you want, at least not with generic systems. In order to share a layer that is applicable to another system, you’d have to ensure that every single piece of that system is exactly the same, from the BIOS up. Think phones getting updates, as that’s very similar.
Not really as you can have a separate boot partition with automatic bootloader updating. One user suggested using rsync to pull any changes. If I’m doing that already I could just have a post install script that gets the system ready.