Sure, docker-compose is great, but could we get similar functionality using just the tools that are built into CoreOS? Can we get automatic updates, too? Yes we can! 📦
      • Rearsays@lemmy.mlEnglish
        101·
        1 year ago

        It’s just morally rough that they basically said they don’t get anything of benefit from contributing to open source despite really owing their start to it

        • poVoq@slrpnk.netEnglish
          713·
          1 year ago

          You mean showing a commitment to open-source and keeping all of their software open-source (when most other “open-source” companies in similar situations switched to non-Free licenses, like Elasticsearch for example)?

  • shadowbert@kbin.social
    2·
    1 year ago

    Dependencies within unrelated projects (ie, sharing a single database container for a few unrelated apps) is something that would be pretty handy, and is missing from compose.

    Auto-updates are cool - but also dangerous… I think there’s something in running watchtower manually like I have been - when something breaks straight after, I know the cause.

      • shadowbert@kbin.social
        1·
        1 year ago

        I don’t really understand what you’re suggesting. Having a seperate compose file for your database would “work”, but you’d lack any of the dependency handling.

  • garrett@infosec.pubEnglish
    12·
    1 year ago

    Honestly, this is kinda making me wanna redeploy a couple app stacks I have on a VPS. Hmm.

  • thevoiceofra@mander.xyzEnglish
    59·
    1 year ago

    Interesting. But what If I’m not using CoreOS? Also RedHat fucked up by using YAML for configuration.

    • losttourist@kbin.social
      12·
      1 year ago

      what if I’m not using CoreOS?

      Podman runs on any distro (or more strictly: any distro that uses systemd). It’s essentially a FOSS alternative to Docker.

      • lemmyvore@feddit.nlEnglish
        211·
        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.

        • losttourist@kbin.social
          11·
          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.

          • lemmyvore@feddit.nlEnglish
            2·
            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 tie containers into systemd units, quadlets just make it easier; but the best practice advice is to not do it at all. 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. There’s no reason to reference docker in this article — unless you’re doing it for the views.

    • poVoq@slrpnk.netEnglish
      3·
      1 year ago

      It’s built into Podman 4.x, so you can easily install it on any distro (with Systemd).