The mentioned auto-update and rollback stuff looks also nice: https://www.redhat.com/sysadmin/podman-auto-updates-rollback...
Make systemd better for Podman with Quadlet
21–30 of 88 posts
Re: Make systemd better for Podman with Quadlet
#22Odd choice using systemd syntax willingly when all other industry tools use YAML, IMO
It's a tool that replaces your usual long systemd unit file with a smaller systemd unit file without boilerplate. Seems like a perfectly good choice to me.
Re: Make systemd better for Podman with Quadlet
#23This looks quite nice. I run a server which is already RHEL+podman+generated systemd units, but this both simpler and more declarative/idempotent than my current setup. Anything that helps convince people that containers running on a single server can be simple, and doesn't require an entire k8s stack.
Re: Make systemd better for Podman with Quadlet
#24Re: Make systemd better for Podman with Quadlet
#25Re: Make systemd better for Podman with Quadlet
#26I heard you like abstract tools to do stuff, so I added an abstract tool to your tool to manage abstract tooling.
This is actually a pretty natural fit, imo. Docker containers are basically processes with fat runtimes, and container orchestration layers are essentially glorified process supervisors.
At the same time, most Linux systems already come with a pretty fancy process supervisor. Personally, I think writing systemd units from scratch is already pretty easy. But it makes sense that Linux software which often integrates with (essentially) process supervisors would want painless integration with systemd!
Also, in some ways I think this is simpler. Anyone who has used a reasonably modern Linux likely has some systemd experience. For local testing and 'orchestration', why rely on some additional one-off layer like docker-compose when the operating system's built-in process supervisor has all of the facilities you need?
Re: Make systemd better for Podman with Quadlet
#27I heard you like abstract tools to do stuff, so I added an abstract tool to your tool to manage abstract tooling.
Terraform run from CI pipeline enters the chat
Re: Make systemd better for Podman with Quadlet
#28Earlier quoted context omitted.
RedHat basically sponsored the development of Systemd (among other things) so their full-throated support isn't surprising also, fwiw, YAML is a data serialization format, not a configuration format. people who use YAML and pretend it's a config file format are either lazy, incompetent, or both.
The industry disagrees with your hot take. Configurations will almost always be serialized into some kind of struct, YAML/JSON/TOML/etc work well for this. The neat part is you can use other tools to do the templating to YAML more intelligently, instead of having each tool DIY their own config templating setup.
Hot take? It's literally a data serialization language. Configuration != data serialization for, like, all of time.
No one is mincing words about YAML being used for configuration rather rampantly. They're saying it's a shitshow, and I agree.
> Configurations will almost always be serialized into some kind of struct
No, this is in fact a fairly modern phenomenon due to what I can only imagine is fear of compilers. The grand tradition is for configuration to be parsed and interpreted, which is rather distinct from serialization. Take your editor, or version control software of choice, or nearly every file in /etc, for example.
Standardizing things can be good, sure, and for all the warts YAML is at least consistent, usually, but it's a trend in the wrong direction.
Treating configuration as data is a Choice. I can hear them saying now "oh but being able to template or write a program to manipulate or edit configuration is so much better" -- take a look at how git config works. You can edit interactively with the CLI, read/write arbitrary fields, and yet it's not structured beyond INI style "key = value". There's no schema, and yet nothing is lost. There's certainly no Norway problem.
Re: Make systemd better for Podman with Quadlet
#29I was just cursing a lot setting up a single node with my default stack. I’m going to try this tomorrow, because containers are so useful, but I just don’t want to deal with K8s on anything that I run myself.
not even k3s?
Re: Make systemd better for Podman with Quadlet
#30I was just cursing a lot setting up a single node with my default stack. I’m going to try this tomorrow, because containers are so useful, but I just don’t want to deal with K8s on anything that I run myself.
I just use docker compose at home for about 15 containers and it works great.