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-sys...
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?
Overall I'm fine with it. My general thoughts are:
1) What value does it provide to the average user over the build int
podman bits to generate systemd services?
2) is it something we ship by default or support by it being easy to
overlay for users that want it
3) I tried to test it via overlay and it doesn't appear to be in
Fedora (didn't look any further to see if it was under review etc)
4) Do we ship it straight up once it's in Fedora, wait until it's
integrated/part of podman, support it as overlay initially and include
it once it's part of podman (you get the gist).
P