{"slug": "podman-quadlet", "name": "Podman Quadlet", "category": "infra", "category_name": "Infrastructure and DevOps", "description": "", "recommenders": 3, "commenters": 3, "warners": 0, "score": 2.776, "rising": 0.35, "first": "2026-05-05", "latest": "2026-10-16", "why": "The nice thing about quadlets is exactly that, they integrate with systemd and by extension the rest of the system.", "why_is_quote": true, "has_verdict": false, "sentiment": {"recommend": 3, "neutral": 0, "compare": 0, "warn": 0}, "spark": [0, 0, 0, 0, 0, 0, 2, 0, 0, 0, 0, 1], "listed": true, "loved": [], "caveat": "", "short_quote": "The nice thing about quadlets is exactly that, they integrate with systemd and by extension the rest of the system.", "kind": "", "icon": true, "domain": null, "github_repo": null, "official_url": "https://docs.podman.io/en/latest/markdown/podman-systemd.unit.5.html", "pricing": "", "aliases": ["Podman Quadlet"], "verdict": null, "praise": [{"label": "", "summary": "", "quotes": [{"id": 802015632, "item_id": 50125977, "url": "https://news.ycombinator.com/item?id=50125977", "by": "LaurensBER", "date": "2026-10-16", "stance": "recommend", "quote": "If you're already using systemd it's barely any effort to add quadlets. Give them a try!", "excerpt": "If you're already using systemd it's barely any effort to add quadlets. Give them a try!", "context": "", "use_case": "", "switched_from": "", "story": "What I self-host"}, {"id": 768421648, "item_id": 48026353, "url": "https://news.ycombinator.com/item?id=48026353", "by": "stryan", "date": "2026-05-05", "stance": "recommend", "quote": "The nice thing about quadlets is exactly that, they integrate with systemd and by extension the rest of the system.", "excerpt": "> Having your whole application with its containers, volumes, and networks all defined together in one easy-to-read YAML file is a way better experience. Deployment is two steps: 1. `git clone foo` 2. `docker compose up -d`. You can see the state of the application containers with `docker compose ps`. You can run multiple compose applications on the same host and manage them separately by putting them in different di", "context": "", "use_case": "running containers as systemd services", "switched_from": "", "story": "Should I Run Plain Docker Compose in Production in 2026?"}, {"id": 768333600, "item_id": 48020850, "url": "https://news.ycombinator.com/item?id=48020850", "by": "whilenot-dev", "date": "2026-05-05", "stance": "recommend", "quote": "and I'd agree, systemd can manage services on a system just fine, and even better than any compose workload ever could.", "excerpt": "GP is talking about podman with generated systemd unit files (a.k.a. podman quadlet[0]), not the docker-compose-compatible podman-compose ...and I'd agree, systemd can manage services on a system just fine, and even better than any compose workload ever could. journald will help with logs, and the pull policy[1] helps with mutable tags. What help do you need with \"orphan containers\"? [0]: https://docs.podman.io/en/la", "context": "", "use_case": "", "switched_from": "", "story": "Should I Run Plain Docker Compose in Production in 2026?"}]}], "caveats": [], "who": [], "tags": [], "use_cases": ["running containers as systemd services"], "compared": [], "makers": [], "threads": [{"url": "https://news.ycombinator.com/item?id=47962032", "title": "Should I Run Plain Docker Compose in Production in 2026?", "mentions": 2}, {"url": "https://news.ycombinator.com/item?id=50109715", "title": "What I self-host", "mentions": 1}], "sentiment_by_month": {"2025-11": {}, "2025-12": {}, "2026-01": {}, "2026-02": {}, "2026-03": {}, "2026-04": {}, "2026-05": {"recommend": 2}, "2026-06": {}, "2026-07": {}, "2026-08": {}, "2026-09": {}, "2026-10": {"recommend": 1}}, "quotes": [{"id": 802015632, "item_id": 50125977, "url": "https://news.ycombinator.com/item?id=50125977", "by": "LaurensBER", "date": "2026-10-16", "stance": "recommend", "quote": "If you're already using systemd it's barely any effort to add quadlets. Give them a try!", "excerpt": "If you're already using systemd it's barely any effort to add quadlets. Give them a try!", "context": "", "use_case": "", "switched_from": "", "story": "What I self-host"}, {"id": 768421648, "item_id": 48026353, "url": "https://news.ycombinator.com/item?id=48026353", "by": "stryan", "date": "2026-05-05", "stance": "recommend", "quote": "The nice thing about quadlets is exactly that, they integrate with systemd and by extension the rest of the system.", "excerpt": "> Having your whole application with its containers, volumes, and networks all defined together in one easy-to-read YAML file is a way better experience. Deployment is two steps: 1. `git clone foo` 2. `docker compose up -d`. You can see the state of the application containers with `docker compose ps`. You can run multiple compose applications on the same host and manage them separately by putting them in different di", "context": "", "use_case": "running containers as systemd services", "switched_from": "", "story": "Should I Run Plain Docker Compose in Production in 2026?"}, {"id": 768333600, "item_id": 48020850, "url": "https://news.ycombinator.com/item?id=48020850", "by": "whilenot-dev", "date": "2026-05-05", "stance": "recommend", "quote": "and I'd agree, systemd can manage services on a system just fine, and even better than any compose workload ever could.", "excerpt": "GP is talking about podman with generated systemd unit files (a.k.a. podman quadlet[0]), not the docker-compose-compatible podman-compose ...and I'd agree, systemd can manage services on a system just fine, and even better than any compose workload ever could. journald will help with logs, and the pull policy[1] helps with mutable tags. What help do you need with \"orphan containers\"? [0]: https://docs.podman.io/en/la", "context": "", "use_case": "", "switched_from": "", "story": "Should I Run Plain Docker Compose in Production in 2026?"}]}