01:27 <baaash[m]> what tool should i be using to pre-bestow certain packages onto a coreos image? I can get most of the configuration I need with my butane/ignition config but at a loss as to how to add packages to the image. I understand I can use rpm-ostree install once i've booted into the system, but that's after the fact... (full message at <https://libera.ems.host/_matrix/media/v3/download/libera.chat/80cc1f2b14ce3d13223adfa607379aefb2e73cd1>)

09:37 <travier[m]> baaash: Short answer: it's not easy yet but we're working on it. Container native ostree should let you change Fedora CoreOS to you liking once it's ready but right now you can only add to it not remove from it. We also don't have a good way to provide pre-build images so you have to install using the current images and then rebase to your custom image build.

09:37 <travier[m]> See https://github.com/coreos/layering-examples

10:27 <aleskandro[m]> hi, where can I find a list of the supported kernel arguments that ignition parses? I'm looking for a way to provide the ignition configuration without requiring other hosts (e.g., local file in one of the FSs), is there any?

10:31 <aleskandro[m]> * requiring other reachable hosts (e.g.,

10:37 <aleskandro[m]> is this the only local possibility? https://github.com/coreos/ignition/blob/main/internal/distro/distro.go#L32

11:01 <travier[m]> aleskandro: You can write your ignition config in /boot like coreos-installer does

11:07 <aleskandro[m]> travier: thanks, any link about that? Any /boot/filename.ign? how can I instruct ignition to take care of it in the kernel args?

11:20 <travier[m]> aleskandro: I can not find the docs. Not sure we document that. Let's wait for US folks to wake up

11:24 <aleskandro[m]> 👍️

13:22 <queeup[m]> aleskandro: as far as I know this is it:... (full message at <https://libera.ems.host/_matrix/media/v3/download/libera.chat/9332d41436e729ef9211d16d6d46a6b6b43cd08c>)

13:23 <queeup[m]> If you want to put it use should_exist, if you want to erase it from kargs use should_not_exist

13:27 <aleskandro[m]> Hi queeup , I want to pass the ignition filepath (not url) via kernel command line (or similar). Looking in the code I found that I could pass ignition.platform.id=file (https://github.com/coreos/ignition/blob/5667e9f1cacaa84af6581f81e1cb8079033b8216/internal/platform/platform.go#L208)

13:27 <aleskandro[m]> to use the file provider and the provider would look for /config.ign in the initramfs. https://github.com/coreos/ignition/blob/0cbe33fee45d012515479a88f0fe94ef58d5102b/internal/providers/file/file.go#L29-L30.

13:27 <aleskandro[m]> It's also possible to patch the path of the ignition config file to be another through an env variable (for example set by the ignition-generator), but some of the units need to start before any other file system is mounted (otherwise, we might not be able to work on the disks via ignition). So it's still in the initrd that I can provide "local" ignition files.

13:30 <aleskandro[m]> what travier was talking about is maybe this https://github.com/coreos/coreos-installer/blob/main/docs/iso-embed-ignition.md which chains an additional initrd image

13:35 <queeup[m]> Yea: This is how I customize my iso images with my own ignition to put on it:... (full message at <https://libera.ems.host/_matrix/media/v3/download/libera.chat/c4d5228517f5f972419f4d47c43fae4f6b7e9e06>)

13:36 <aleskandro[m]> and if i understand correctly, it fills the additional initrd so that when you boot, you'll get the config.ign file set to provision the host with the content of your myconfig.ign

13:39 <queeup[m]> I don't know the technical details but When I put myconfig.ign to iso if I boot it It start installing and provision my config.

14:05 <aleskandro[m]> I succeeded by using:... (full message at <https://libera.ems.host/_matrix/media/v3/download/libera.chat/541c50572ac9831ed41f78528b4d0065c24eda62>)

14:06 <aleskandro[m]> * I succeeded by using:... (full message at <https://libera.ems.host/_matrix/media/v3/download/libera.chat/590491b9d75bdb0abf6aa193124fa31d29f3bbf2>)

14:25 <travier[m]> aleskandro: You're re'making something that we already have and does that by pulling the config from the /boot partition

14:25 <travier[m]> s/'/-/

14:26 <travier[m]> I'd recommend making an installation via the LiveISO with an Ignition and then looking at the content of the partitions to see where the config is stored until we link the details here

14:29 <aleskandro[m]> > Yea: This is how I customize my iso images with my own ignition to put on it:... (full message at <https://libera.ems.host/_matrix/media/v3/download/libera.chat/712c8109488256f8666aec2a7061bc648ddf46d6>)

14:29 <travier[m]> This embeds an ignition configuration inside an ISO

14:30 <travier[m]> What I mean is booting a default live iso, manually doing the installation via coreos-installer and then looking at the boot partition content

14:31 <aleskandro[m]> 👍️

15:32 <dustymabe> jlebon: do you want to check the most recent upload I did on https://github.com/coreos/fedora-coreos-tracker/pull/1331 ?

16:35 <jlebon> dustymabe: reviewed

17:09 <jaimelm> travier[m]: You coming to the OKD meeting?

17:13 <travier[m]> jaimelm: whoops, joining

17:16 <travier[m]> jaimelm: I get "invalid passcode" :/

17:22 <jaimelm> https://umich.zoom.us/j/98508155508?pwd=NXVjVk1wOE5CM2hsRDQ4eGh5eUdhZz09

20:37 <baaash[m]> <travier[m]> "See https://github.com/coreos/..."; <- thank you for your reply. I appreciate the complexity involved, and all the work put in to this project. The Ansible route will suffice, and the anisble-firewalld example, from the link you shared, demonstrates what needs to be done very clearly. thanks again.