Make systemd better for Podman with Quadlet
1–10 of 88 posts
Re: Make systemd better for Podman with Quadlet
#2I 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.
Re: Make systemd better for Podman with Quadlet
#3[deleted]
Re: Make systemd better for Podman with Quadlet
#4Odd choice using systemd syntax willingly when all other industry tools use YAML, IMO
Re: Make systemd better for Podman with Quadlet
#5I heard you like abstract tools to do stuff, so I added an abstract tool to your tool to manage abstract tooling.
Re: Make systemd better for Podman with Quadlet
#6Odd choice using systemd syntax willingly when all other industry tools use YAML, IMO
You can apparently use kubernetes YAML with a .kube target and podman will orchestrate the containers, service, volumes appropriately (on a single node). The only systemd config is a minimal boilerplate to point at the kubernetes YAML.
Re: Make systemd better for Podman with Quadlet
#7Huh, this exactly what I’ve been looking for recently for some local/home-network/homelab setups, even down to the use of systemd-like ini/toml syntax.
Re: Make systemd better for Podman with Quadlet
#8Odd choice using systemd syntax willingly when all other industry tools use YAML, IMO
You can apparently use kubernetes YAML with a .kube target and podman will orchestrate the containers, service, volumes appropriately (on a single node). The only systemd config is a minimal boilerplate to point at the kubernetes YAML.
You are correct. And there is an Ansible role for automated management: https://github.com/linux-system-roles/podman/
Re: Make systemd better for Podman with Quadlet
#9Odd choice using systemd syntax willingly when all other industry tools use YAML, IMO
For this, systemd syntax is a lot better than yaml IMO.
In fact, I'd prefer if the tools you mentioned used something else besides yaml.
Re: Make systemd better for Podman with Quadlet
#10Odd choice using systemd syntax willingly when all other industry tools use YAML, IMO
It seemed to me that the original target audience for this is users already familiar with systemd's unit syntax, so making these "unit files" use it as well was a sensible choice.