I like this idea, but maybe we should just wait (or even help push) for the upstream podman integration (https://github.com/containers/quadlet/issues/11)?

On Fri, May 6 2022 at 03:40:35 PM -0400, Matthew Miller <mattdm@fedoraproject.org> wrote:
In short: quadlet is a systemd generator which makes it easy to define container options in simple systemd-style config file, from which corresponding systemd units are created on the fly. This seems like an ideal way to manage single-node (or otherwise stand-alone) container setups. Right now, I'm using a bunch of files created with `podman generate systemd`, and while that works, it's also kind of a management mess. See https://blogs.gnome.org/alexl/2021/10/12/quadlet-an-easier-way-to-run-system-containers/ for an intro post and the project at https://github.com/containers/quadlet. Smooge has packaged this into the main repo -- Rawhide but F36 build coming soon. I propose: 1. We include this in the base ostree package set. 2. We document it as the primary way to set up containers on Fedora IoT for single / independent systems. 3. We provide feedback to the project on how this could serve real-world use cases better. What do you all think? -- Matthew Miller <mattdm@fedoraproject.org> Fedora Project Leader _______________________________________________ IoT mailing list -- iot@lists.fedoraproject.org To unsubscribe send an email to iot-leave@lists.fedoraproject.org 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/iot@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure