04:37 <jobcespedes[m]> Hi, can I config two Zincati upgrade strategies at the same time: periodic and fleetlock? So upgrades are orchestrated in time windows only

07:06 <JohnnyArcitec[m4> Is there any way to make a "rpm-ostree compose" treefile that pulls in the existing OCI images of Fedora Silverblue and just adds some more OCI layers on top of it for extra packages/modifications? So that I don't have to compose the entirety of Silverblue from scratch locally?

07:09 <JohnnyArcitec[m4> If that isn't possible, then what suggestions do you have for making Silverblue derived OCI images via "rpm-ostree compose"? (It's important to use that tool, to get deterministic builds and de-duplicated package-layers since I'm adding around 1.2GB of packages and don't want to ship all of them every day, only when they change.)

07:11 <JohnnyArcitec[m4> * If that isn't possible, then what suggestions do you have for making Silverblue derived OCI images via "rpm-ostree compose"? (It's important to use that tool, to get deterministic builds and de-duplicated package-layers since I'm adding around 1.2GB of packages and don't want to ship all of those "package group" OCI layers every day, only when they change.)

07:23 <JohnnyArcitec[m4> * If that isn't possible, then what suggestions do you have for making Silverblue derived OCI images via "rpm-ostree compose"? (It's important to use that tool, to get deterministic builds and de-duplicated package-layers since I'm adding around 1.2GB of packages and don't want to ship all of those extra "package group" OCI layers every day, only when they change.)

07:23 <JohnnyArcitec[m4> * If that isn't possible, then what suggestions do you have for making Silverblue derived OCI images via "rpm-ostree compose"? (It's really important to use that tool, to get deterministic builds and de-duplicated package-layers since I'm adding around 1.2GB of packages and don't want to ship all of those extra "package group" OCI layers every day, only when they change.)

07:25 <JohnnyArcitec[m4> * If that isn't possible, then what suggestions do you have for making Silverblue derived OCI images via "rpm-ostree compose"? (It's really important to use that tool, to get deterministic builds and de-duplicated package-layers since I'm adding around 1.2GB of packages and don't want to ship all of those extra "package group" OCI layers every day if their package versions didn't even change.)

07:25 <JohnnyArcitec[m4> * If that isn't possible, do you have any suggestions for making Silverblue derived OCI images via "rpm-ostree compose"? (It's really important to use that tool, to get deterministic builds and de-duplicated package-layers since I'm adding around 1.2GB of packages and don't want to ship all of those extra "package group" OCI layers every day if their package versions didn't even change.)

07:26 <JohnnyArcitec[m4> * If that isn't possible, do you have any suggestions for making Silverblue derived OCI images via "rpm-ostree compose"? (It's really important to use that tool, to get deterministic builds and de-duplicated package-layers since I'm adding around 1.2GB of packages and don't want to ship all of those extra "package group" OCI layers every day if their package versions didn't even change.) 🙂

07:28 <JohnnyArcitec[m4> * If that isn't possible, do you have any suggestions for efficiently making Silverblue derived OCI images via "rpm-ostree compose"?

07:28 <JohnnyArcitec[m4> (It's really important to use that tool, to get deterministic builds and de-duplicated package-layers since I'm adding around 1.2GB of packages and don't want to ship all of those extra "package group" OCI layers every day if their package versions didn't even change.) 🙂

07:29 <JohnnyArcitec[m4> * If that isn't possible, do you have any suggestions for efficiently making Silverblue derived OCI images via "rpm-ostree compose"?

07:29 <JohnnyArcitec[m4> (It's really important to use that tool, to get deterministic builds and de-duplicated package-layers since I'm adding around 1.2GB of packages and don't want to ship all of those extra "package group" OCI layers every day if their package versions didn't even change.) 🙂

07:35 <JohnnyArcitec[m4> * If that isn't possible, do you have any suggestions for efficiently making Silverblue derived OCI images via "rpm-ostree compose"?

07:35 <JohnnyArcitec[m4> (It's really important to use that tool, to get deterministic builds and de-duplicated package-layers since I'm adding around 1.2GB of packages and don't want to ship all of those extra "package group" OCI layers every day if their package versions didn't even change.) 🙂

07:35 <JohnnyArcitec[m4> In a worst case scenario, I'd be able to survive with just the ability to somehow import Silverblue's tree file into my own so that I don't have to write a copy of the official Silverblue spec manually.

07:36 <JohnnyArcitec[m4> * If that isn't possible, do you have any suggestions for efficiently making Silverblue derived OCI images via "rpm-ostree compose"?

07:36 <JohnnyArcitec[m4> In a worst case scenario, I'd be able to survive with just the ability to somehow import Silverblue's tree file into my own so that I don't have to write a copy of the official Silverblue spec manually.

07:36 <JohnnyArcitec[m4> Any ideas would be much appreciated.

07:36 <JohnnyArcitec[m4> (It's really important to use that tool, to get deterministic builds and de-duplicated package-layers since I'm adding around 1.2GB of packages and don't want to ship all of those extra "package group" OCI layers every day if their package versions didn't even change.) 🙂

07:39 <JohnnyArcitec[m4> * If that isn't possible, do you have any suggestions for efficiently making Silverblue derived OCI images via "rpm-ostree compose"?

07:39 <JohnnyArcitec[m4> (It's really important to use that tool, to get deterministic builds and de-duplicated package-layers since I'm adding around 1.2GB of packages and don't want to ship all of those extra "package group" OCI layers every day if their package versions didn't even change.) 🙂

07:39 <JohnnyArcitec[m4> In a worst case scenario, I'd be able to survive with just the ability to somehow import Silverblue's tree file into my own so that I don't have to write a copy of the official Silverblue spec manually.

07:39 <JohnnyArcitec[m4> Any ideas would be incredibly appreciated.

07:51 <travier[m]> Johnny Arcitec: If you're pulling an OCI image as a base, then you have to use container layers via a Containerfile. Otherwise, when using manifests, you have to rebuild the whole thing.

12:04 <walters> Johnny Arcitec: Definitely thought about this several times, just filed https://github.com/coreos/rpm-ostree/issues/4427

15:23 <JohnnyArcitec[m4> <travier[m]> "Johnny Arcitec: If you're..." <- Yeah that's what I feared. And containerfiles aren't "smart enough" to know when package-content layers have truly changed, so we end up shipping 1.2gb of "modified layers" every day. :(

15:26 <JohnnyArcitec[m4> <walters> "Johnny Arcitec: Definitely..." <- Thank you so much Colin for considering this. I've been watching the work on CoreOS and you're an absolute genius.

15:26 <JohnnyArcitec[m4> In the meantime, what's the easiest way to base something on Silverblue's OCI images? I don't even know where the official treefiles are (in a git repo somewhere, hopefully). Perhaps I can make a build tool in the meantime which pulls that treefile, and uses something like Python to merge my on changes into the treefile to build my on Silverblue OCI from scratch.

15:27 <JohnnyArcitec[m4> > <@walters:fedora.im> Johnny Arcitec: Definitely thought about this several times, just filed https://github.com/coreos/rpm-ostree/issues/4427

15:27 <JohnnyArcitec[m4> * Thank you so much Colin for considering this. I've been watching the work on CoreOS and you're an absolute genius.

15:27 <JohnnyArcitec[m4> In the meantime, what's the easiest way to base something on Silverblue's OCI images *via treefiles*? I don't even know where the official treefiles are (in a git repo somewhere, hopefully). Perhaps I can make a build tool in the meantime which pulls that treefile, and uses something like Python to merge my on changes into the treefile to build my on Silverblue OCI from scratch.

15:27 <walters> (Since this is not coreos related, we could use the #fedora-devel channel too)

15:27 <walters> But anyways it's https://pagure.io/workstation-ostree-config/ and this is an example in https://coreos.github.io/rpm-ostree/container/#creating-base-images

15:28 <JohnnyArcitec[m4> * Thank you so much Colin for considering this. I've been watching the work on CoreOS and you're an absolute genius.

15:28 <JohnnyArcitec[m4> In the meantime, what's the easiest way to base something on Silverblue's OCI images _via treefiles_? I don't even know where the official treefiles are (in a git repo somewhere, hopefully). Perhaps I can make a build tool in the meantime which pulls that treefile, and uses something like Python to merge my own changes into the treefile to build my own Silverblue OCI from scratch.

15:29 <JohnnyArcitec[m4> walters: Thank you very much, I'll experiment with getting that to build, and hopefully won't run into any "lack of digital signature" issues when making "from scratch" like this.

15:29 <JohnnyArcitec[m4> > <@walters:fedora.im> But anyways it's https://pagure.io/workstation-ostree-config/ and this is an example in https://coreos.github.io/rpm-ostree/container/#creating-base-images

15:29 <JohnnyArcitec[m4> * Thank you very much, I'll experiment with getting that to build, and hopefully won't run into any "lack of Fedora's digital signatures" issues when making "from scratch" like this.

22:54 <oo> Does anyone use coreos as a development machine? I like the idea, not sure about practicality