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?

  • ZeDoTelhado@lemmy.worldEnglish
    0·
    2 months ago

    I actually tried to switch to podman from docket but I have a major hold up. On my docker setup for my arr stack I have gluetun, and basically how I setup gluetun with the rest is setting up ports on gluetun for the services and for the other services I have a depends on, to make sure gluetun is up before the rest. However I tried to look several times how to do this on podman but no luck. Does anyone here has an idea how this works?

    • 4am@lemmy.zipEnglish
      5·
      2 months 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
        04·
        2 months 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
          31·
          2 months 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
            11·
            2 months 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
              11·
              2 months 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
                    11·
                    2 months 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.