Docker is hard work - Lemmy
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?
Podman is an alternative to Docker which integrates better with systemd and it also offers a way to automatically update containers.
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?
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.
trilobite
exu