←back to thread

Podman Quadlets with Podman Desktop

(podman-desktop.io)
180 points teleforce | 4 comments | 14 Apr 25 17:16 UTC | HN request time: 0s | source
Show context
orthoxerox ◴[14 Apr 25 20:20 UTC] No.43685880[source]▶
What is the killer feature that will make me want to switch from Docker Compose to Podman Quadlets?
replies(7): >>43685989 #>>43685992 #>>43686728 #>>43687129 #>>43687706 #>>43688911 #>>43690483 #
dharmab ◴[14 Apr 25 20:32 UTC] No.43685989[source]▶
I prefer quadlet for 2 reasons:

1. Podman is simpler than Docker. There is no long-running daemon. Rootless is default.

2. Quadlets can be managed as systemd services, giving me the same tools to manage and view logs for system daemons and containers.

Quadlets have been especially nice for bundling up an AI app I wrote as a cloud-init file, making it easy to deploy the hardware, software and models as one artifact.

replies(2): >>43686670 #>>43687155 #
pydry ◴[14 Apr 25 21:46 UTC] No.43686670[source]▶
quadlets == systemd which requires root to run. this is NOT the same thing as "systemd cant run non root containers". OBVIOUSLY it can, just as docker can run non root containers.

Making systemd a necessary dependency to run > 1 container kinda negates many of the the nice advantages that podman has of not requiring root.

podman compose doesnt require root and would serve as a substitute but it's a very neglected piece of software.

replies(3): >>43686855 #>>43686924 #>>43686928 #
voxadam ◴[14 Apr 25 22:21 UTC] No.43686924[source]▶
systemd user units can be run by non-root users.

https://wiki.archlinux.org/title/Systemd/User

replies(1): >>43686977 #
pydry ◴[14 Apr 25 22:29 UTC] No.43686977[source]▶
not the point as i mentioned above.

systemd itself requires root.

replies(3): >>43687015 #>>43687216 #>>43687686 #
dharmab ◴[15 Apr 25 00:12 UTC] No.43687686[source]▶
How were you planning to run podman compose without an init process running as root?
replies(1): >>43689997 #
pydry ◴[15 Apr 25 07:35 UTC] No.43689997[source]▶
what else would you like to bundle in the init process? docker compose as well? maybe kubernetes too. a webserver? a word processor perhaps? maybe an email client?
replies(2): >>43691084 #>>43691476 #
robertlagrant ◴[15 Apr 25 10:45 UTC] No.43691084{3}[source]▶
Podman compose isn't bundled in the init process.
replies(1): >>43692093 #
1. pydry ◴[15 Apr 25 13:04 UTC] No.43692093{4}[source]▶
Yep, but have you used it? It's crap. It implements about half of what docker compose does.

I'd stop complaining about quadlets being a hunk of crap if podman compose were decently maintained.

replies(1): >>43692555 #
2. robertlagrant ◴[15 Apr 25 13:40 UTC] No.43692555[source]▶
I'm contesting your claim that podman compose is bundled with systemd.
replies(1): >>43694811 #
3. pydry ◴[15 Apr 25 16:04 UTC] No.43694811[source]▶
I never made this claim.
replies(1): >>43702981 #
4. robertlagrant ◴[16 Apr 25 08:35 UTC] No.43702981{3}[source]▶
So what was this about? What's the thing that the "else" refers to?

> what else would you like to bundle in the init process? docker compose as well? maybe kubernetes too. a webserver? a word processor perhaps? maybe an email client?