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?

  • jabberwock@lemmy.dbzer0.comEnglish
    0·
    7 days ago

    Short version, add this to your Quadlet file (with whatever your service your gluetun Quadlet starts):

    [Unit]
Requires=gluetun.service
After=gluetun.service

    An article I found helpful when starting with Quadlets, which can even replace Docker compose. https://mo8it.com/blog/quadlet/

      • MalReynolds@slrpnk.netEnglish
        0·
        7 days ago

        Been using an quadlet podman arr stack for a year or two, pretty damn bulletproof once set up, easier to read, rootless, SELinux enabled, systemd controlled, update with podman auto-update. Worth the time to learn.

        podlet can help you hit the ground running. It can create Quadlet files out of Podman commands or even (Docker) Compose files. 90% of the time it works every time ;}, but even the oopses get you most of the way there.

        My arr stack is set up in a pod which means they all have their own gluetun network and come up as one, but you can just use Network=container:gluetun in container files.