I don’t really have anyone else to shout at about this, but it’s an amazing way to host services in rootless containers entirely in user space using systemd (systemctl --user).
https://docs.podman.io/en/latest/markdown/podman-systemd.unit.5.html
I don’t really have anyone else to shout at about this, but it’s an amazing way to host services in rootless containers entirely in user space using systemd (systemctl --user).
https://docs.podman.io/en/latest/markdown/podman-systemd.unit.5.html
They are generally pretty good but troubleshooting them is a pain. Quadlets are also a bit more more complex than Docker compose.
Note: User space includes root and anything not running in kernel space.
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 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.