Comment on Quadlets might make me finally stop using docker-compose

• lemmyvore@feddit.nl ⁨1⁩ ⁨year⁩ ago

  …except I can run Docker anywhere. It’s not tied to systemd. These quadlets seem like a very systemd-specific thing. Which is great if you’re building everything around systemd but it’s a niche.

  source

  • losttourist@kbin.social ⁨1⁩ ⁨year⁩ ago

    systemd [is] a niche

    Maybe in the wider world of all the operating systems installed on all the computers, but for Linux-based computing it is, like it or not, near ubiquitous these days. And in particular for server systems (and this is, after all, /m/selfhosted), good luck finding something that isn't systemd-based unless you're deliberately choosing a BSD or aiming for a system which has ever-decreasing amounts of support available.

    source

    • lemmyvore@feddit.nl ⁨1⁩ ⁨year⁩ ago

      This being selfhosted is exactly the reason I would’ve expected people to be aware there’s more variety out there. systemd is not as ubiquitous as you make it sound.

      Secondly, tying your containerization solution into your init system is a spectacularly bad idea. You could already do this with docker; the best practice is to not do it. You have a restart policy built into docker/podman for a reason. Let the init system deal with podman/docker itself, and let podman/docker manage their containers.

      Third, the article title is misleading; if anything it should say quadlets made them give up podman-compose, not docker-compose.

      source