Well, after a while in the container world ive come to realise that keeping all these containers up to date is hard work and time consuming with simple docker compose. I’ve recently learnt that portainer may come to hand here. I believe that feeding the yaml file through portainer allows the latter to take control of updates. Correct?

I have a Truenas Scale machine with a VM running my containers as i find its the easiest approach for secure backps as i replicate the VM to another small sever just in case.

But i have several layers to maintain. I dont like the idea of apps on Truenas as I’m worried i dont have full control of app backup. Is there a simpler way to maintain my containers up to date?

  • 4am@lemmy.zipEnglish
    0·
    7 days ago

    Since Podman is based around systemd services managing the containers, why not have a look at systemd .service files? I know you can set dependencies in those and so you can say that your other containers can’t start unless gluetun successfully starts first.

    • greyscale@lemmy.grey.oooEnglish
      0·
      7 days ago

      Yaknow, now that I know its tightly coupled to systemd I especially don’t care about podman. Thank you genuinely for resolving any curiosity about it, however.

      • UnityDevice@lemmy.zipEnglish
        0·
        7 days ago

        It’s not tightly coupled to anything. It just ships with a systemd generator allowing you to manage containers, pods or networks with systemd if you want. And lots of people are noticing the benefits of that arrangement.

        • greyscale@lemmy.grey.oooEnglish
          0·
          7 days ago

          That sounds heavy and complicated. Terraform + plain docker is super easy and makes the machines trivial to replace, as well redeploying updating their containers without downtime.

          And I don’t have to learn a damn thing about systemd’s nonsense. Nor do I have to learn a single bit of k8s yaml braindamage.

          • UnityDevice@lemmy.zipEnglish
            0·
            7 days ago

            That sounds heavy and complicated.

            It’s neither. A systemd generator just transforms a simple 15 line container text file to a simple 20 line service text file, and then the container lifecycle and dependencies are managed by systemd like any other system or user service.

                • greyscale@lemmy.grey.oooEnglish
                  0·
                  7 days ago

                  You’re adding piles of nonsense ontop of nonsense.

                  None of it actually gets you closer to your objective.

                  Reduce and simplify. k8s and whatever the hell it is you’re doing is very much the opposite of that. enjoy yaml hell.

                  • UnityDevice@lemmy.zipEnglish
                    0·
                    7 days ago

                    My friend, a podman container file is a simple tiny ini text file. Behind the scenes it gets converted to a systemd service unit file, which is also an ini text file. The service file has a simple ExecStart command that just calls podman run. Meanwhile podman will just set up an environment and run the container with runc or crun. The whole thing is basically one step above a shell script. I could buildroot a system with this entire stack and it would fit on my wifi router.

                    You’re the one overcomplicating things.