On Sun, Jan 16, 2022 at 8:43 AM Josh Boyer <jwboyer@xxxxxxxxxxxxxxxxx> wrote: > > > > On Sat, Jan 15, 2022, 6:57 PM Kevin Fenzi <kevin@xxxxxxxxx> wrote: >> >> On Thu, Jan 13, 2022 at 02:14:19PM -0500, Neal Gompa wrote: >> > >> > One of the things that has recently happened in the Koji space is the >> > addition of a kiwi-build task to build images using the KIWI tool[1]. >> > >> > KIWI supports building all kinds of operating system images, including >> > OCI containers. The Fedora Cloud WG is poking at the idea of using >> > KIWI for the cloud image to replace the unmaintained and brittle >> > ImageFactory, and we could also look at doing container builds with >> > KIWI to replace the OpenShift Atomic Reactor system. That would >> > drastically simplify the architecture and make container image builds >> > considerably more reasonable for the Container SIG and any other >> > stakeholders. >> >> Yeah, thats quite interesting. I would be happy to move to a pipeline >> thats less fragile here. :) >> >> There's also talk about moving things to use ImageBuilder, but I don't >> think it does containers. > > > We can, and should, have RFEs for Image Builder to do containers. I know we need this internally as well. It may farm that out to buildah in the background or something, but that remains to be determined. > The "Image Builder" architecture is almost as bad as OpenShift Atomic Reactor. It requires a whole separate service architecture and can't directly execute inside of a Koji mock environment. That means that it's almost as difficult and fragile to keep up with. Moreover, it can't do nearly all of the image types that Fedora needs, notably live media, install DVDs, or container images. The only thing it does that almost all other tools do not is RPM-OSTree commits. I would like OSBuild to work in Fedora the same way most of our other image build tools do: fork+exec in dynamically spun up mock roots rather than several services across multiple dedicated machines. The ones that don't follow that pattern tend to be the poorly maintained ones, such as ImageFactory and OpenShift Atomic Reactor. > In the interest of commonality across the Fedora/CentOS/RHEL ecosystem, I really think using Image Builder as the tool to build images is the best approach. > In the interest of the Fedora ecosystem, we should use the best tools that people can use. But also keep in mind that we don't have to use a single tool for all the Fedora's image tooling. Heck, right now we use over half a dozen different ones (including different tools for producing RPM-OSTree commits depending on the Fedora variant). Going down to 2 or 3 that are much easier for people to self-host and run is better than the current situation. -- 真実はいつも一つ！/ Always, there's only one truth! _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
