• Lem453@lemmy.ca
    link
    fedilink
    English
    arrow-up
    0
    arrow-down
    1
    ·
    edit-2
    1 month ago

    Why would someone want containers managed by systemd instead of just having them run like normal? What is the advantage?

    Also if you use cockpit or some equivalent GUI to manage your containers, do you have to give it permission to control all systemd services?

    • Chais@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 month ago

      Why would you not want containers managed by systemd?
      You get the benefits of containerisation and you don’t have to learn the arcane syntax of some container engine or another.

    • exu@feditown.com
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 month ago

      I’ve been managing my containers using the older mechanism (systemd-generate) since I started and it’s great. You get the reliable service start of systemd and its management interface. Monitoring is consistent with all your other services and you have your logs in exactly one location.

      I really wouldn’t want a separate interface or service manager just because I’m running containers.

      • Lem453@lemmy.ca
        link
        fedilink
        English
        arrow-up
        0
        ·
        1 month ago

        Do you run other things on your system other than containers? I have a VM that only runs containers so it really doesn’t do anything else with systemd apart from the basics so I’m curious if there would be any advantage to me switching.

        • exu@feditown.com
          link
          fedilink
          English
          arrow-up
          1
          ·
          1 month ago

          Most VMs only run containers, but I have supporting services on every host as well. Stuff like the mesh VPN, monitoring agent or firewall.
          If I want a quick overview, a quick systemctl status will tell me everything I need to know.