08:05 <jbtrystram[m]> Friday I've been reading about ignition and thought I'd set up a coreOS VM with a pi-hole service as a learning exercise. But now that I think about it, I realize that ignition is not the correct tool to set up runtime applications is it? Is it more a job for ansible ? I could use ignition to set up a [Container] systemd service, but can I do podman secrets with ignition ?

09:17 <travier[m]> <job[m]> "https://paste.centos.org/view/05..."; <- > <@job:plabble.org> https://paste.centos.org/view/0575e492 - `journalctl -u zincati`

09:17 <travier[m]> 404

09:17 <travier[m]> > Are these normal or is my zincati install broken?

09:18 <travier[m]> jbtrystram: We don't have Python in Fedora CoreOS so Ansible support is limited. You can setup anything you like via Ignition, even application containers. Some examples: https://github.com/travier/fedora-coreos-matrix & https://github.com/travier/fedora-coreos-nomad

09:45 <jbtrystram[m]> travier: thanks for the examples ! Cool to see how you've used the makefile to populate secrets. A builtin support in butane would be cool :)

09:56 <travier[m]> jbtrystram: https://discussion.fedoraproject.org/t/overlaying-libvirt-on-silverblue-kinoite-sericea-onyx-and-coreos/86312 > Related to libvirt setup on rpm-ostree systems

14:44 <mizmo> Hi, any ideas if podman 4.6 would hit the next Fedora Core OS release? it would be very nice 🥺🥺🥺🥺

14:45 <mizmo> (also we should update this rooms icon!)

14:48 <travier[m]> First step is to get it in stable repos: https://bodhi.fedoraproject.org/updates/FEDORA-2023-25546baa8d

14:53 <mizmo> travier: is that a 5 days from now no matter what, or does additional testing with karma expedite that?

14:57 <travier[m]> If you get the requested karma on the update then it goes in faster

14:57 <travier[m]> It will then land in the next Fedora CoreOS testing release, and two weeks later in the next stable release

16:01 <job[m]> My fault, here is a re upload of the logs

16:08 <dgilmore> do we have any stats on fcos user numbers?

18:17 <willbicks> Just starting to explore FCOS and generally finding the docs to be very helpful, thanks all to all involved! I'm exploring using it as a host for k3s when deploying to both VirtualBox and AWS.

18:17 <willbicks> If possible, I'd like to be able to reduce the amount that has to be downloaded at boot time (e.g. executable binaries, RPMs, etc), and instead bake some dependencies into my VirtualBox image / AMIs, while still deferring Ignition configuration to the the later first boot. Seems like it would be beneficial to both reduce time to launch and reduce

18:17 <willbicks> external network dependencies.

18:18 <willbicks> I have familiarity with Packer, but it seems like it might conflict with Ignition's one-shot approach and FCOS's immutable design. I did find `coreos-assembler` but it's README calls out slightly different use cases. Is customizing images for this kind of application something that can be done / is advisable to do? Is there an alternate approach I

18:18 <willbicks> should be considering instead?

18:36 <walters> willbicks: you may be interested in https://github.com/coreos/layering-examples

18:53 <willbicks> +walters: Thanks for the resource, that looks like a solution for exactly what I'm trying to accomplish. It seems like it would still load the overlay from the network but it at least reduces compute at launch time. I also see it marked as "experimental" in a few spots, but I'll give it a try!

19:52 <dustymabe> willbicks: if a lot of your "dependencies" are just container images (i.e. you pull a bunch of containers from the network on boot) the you could just create an EBS volume that is your container storage and mount it under /var/lib/containers.

20:15 <walters> Hmm, an EBS volume mounted that way will only work with a single machine; the general approach here I think is to cache resources inside the infrastructure, which can be done multiple ways. One is to run a quay instance as a pull-through cache https://access.redhat.com/documentation/en-us/red_hat_quay/3.7/html/use_red_hat_quay/quay-as-cache-proxy

21:49 <Nemric> o/ Is there a way, as simple as possible, to know which packages will be on future releases please ?

21:50 <Nemric> I mean latest podman version 4.6.0 ^^

21:52 <Nemric> :/ i thinks that's it : https://builds.coreos.fedoraproject.org/browser?stream=next&arch=x86_64

21:52 <Nemric> thanks ! ;p