Thank you, I think the “less heavy than managing a local micro-k8s cluster”-part was a great portion of what I was missing here.
Comment on The purpose of podman quadlets?
just_another_person@lemmy.world 1 month ago
It’s a systemd-style way to manage podman containers that aims to be as easy to manage as compose/swarm. Not quite an integration, but operates similarly, and about as easy to read. Less heavy than managing a local micro-k8s cluster. That’s about it.
dont@lemmy.world 1 month ago
mosiacmango@lemm.ee 1 month ago
Yup. I read it as “compose and manage containers with systemd.”
Sure, there is a k8s layer abstracted into podman to do this, but you don’t manage or interact with it. Everything is systemd unit file. Containers are started and logged like services.
Easy, direct, tidy.
dont@lemmy.world 1 month ago
Understood, thanks, but if I may ask, just to be sure: It seems to me that without interacting with the kubernetes layer, I’m not getting pods, only standalone containers, correct? (Not that I’m afraid of writing kube configuration, as others have inferred incorrectly. At this point, I’m mostly curious how this configuration would be looking, because I couldn’t find any examples.)
mosiacmango@lemm.ee 1 month ago
I’m still new to this myself, but yes that’s the gist of it. This isn’t k8s or even k3s. It’s an easy, way to declaratively deploy a container on a single node system by using the already present systemd for management. It let’s you pretend that Linux handles containers natively like it does daemons.
This article from redhat has more information about the why and what.