I didn’t use that! I had a docker-compose file and used podlet to translate (which took a little massaging due to it not supporting interpolations).

/usr/libexec/podman/quadlet --user --dryrun was quite helpful though!

Yeah replacing my k3s -> microk8s -> k3s multi-month headache with like 5 basic quadlet files in an evening was so wonderful and a relief

I used podlet on my compose file. I was a little disappointed in the limitations, as a lot of things like variable interpolation isn’t available.

That said, the output made me wonder why I’ve waited! It was so much simpler than I imagined. It also helped demystify unit files a bit more.

Thank you for telling me about Podlet. I’ve been using podman-compose for all my containers but I’ve thought about converting them to systemd units. The only thing I’m unsure about is whether it’ll still be easy to access the container files. Currently I have a containers folder with a folder for each service inside it. Inside that, there’s the compose.yml and the folders with the container data. I map all container folders, with data that needs to be kept, to a folder that sits right next to the compose file. If it’s just temporary data (like caches), I oftentimes map it to a volume because it doesn’t matter if I lose it. Do you know if I can still do it like this (or in a similar way) if I use systemd units?

I’m definitely interested in your experience and why you came to those conclusions because I’m not sure I can agree on the primary points.

But I have to give you the note. Root is also user space (if privileged). I’ve barely ever done anything actually in kernel space, so I guess it’s easy for me to screw that up.

Yeah I agree.

I moved my stack from podman run to quadlets, but god damn was it frustrating to deal with them. I kept running into weird issues such as: the containers not starting every time on reboot, all containers taking like two minutes to start even without needing to download the image, the unit files not being found by systemd.

I ended up moving back to podman run, because they just worked. It is a shame, to be honest, because I would like to use quadlets.

I hate docker compose and find that much more complicated. It’s a whole other structure that’s essentially unneeded.

But I started with podman and not docker, so that’s probably why

I’m now running quadlets on Garuda (my gaming/devbox), and Fedora. The impetus for this was needing to host service in an unprivileged way at work on RHEL9, so I got paid to do some learning with my own services.

My laptop is running Bazzite, but no services there. I’ll move the server to silverblue or another image based distro when I finish extracting the rest of my misadventures to containers.

ucore (soon to be cayo) on my home server!

Just want to chime in here to say I use containerized caddy as a reverse proxy with quadlets and did nothing special.

Agreed! That would be a huge QoL improvement (and work just like the podman command does). Now I’m thinking about other commands that force this silliness, like pip.