A good potential contrast for FCOS is having this be Butane sugar.
On a different vein, since this project hardcodes invoking podmanand there’s already podman generate systemd, this could also just be part of podman directly (e.g. the binary could run as a systemd generator).
The really great thing that it could add is the management of “user level services”, enabling them as part of ignition process ^^ and the last time I looked for quadlet it wasn’t managed
my 2 “golden” cents
I’m sure this will all be ironed out over time, but the reason I asked about “best practices” was for three reasons (so far ).
Since quadlet generated service files do not pull images, is the best approach a one-shot systemd file such as below? While this is sure to slow down the first boot, I’m not sure of a better way.
Description=Pull OCI images for use with podman-quadlet
After=network.target network-online.target nss-lookup.target
ExecStart=/usr/bin/podman pull docker.io/portainer/portainer-ce:latest
ExecStart=/usr/bin/podman pull docker.io/library/caddy:latest
ExecStart=/usr/bin/podman pull docker.io/vaultwarden/server:latest
ExecStart=/usr/bin/podman pull ghcr.io/klutchell/unbound:latest
I haven’t had any luck getting quadlet to auto-create directories and have had to resort to using named volumes. Perhaps this functionality doesn’t exist, or maybe it has to do with directory ownership and/or SELinux. I really should pick up Dan’s book to understand this all better. For example, the below example only works if I manually create all four subdirectories beforehand.