Prevent Stack Restart

[rbrussell82]

I apologize if this is a dumb question, but I didn't see it mentioned in the documentation unless I'm just missing it.

Is there a flag that will download the image updates but not restart the entire stack after each container image is updated?

I use Docker Compose, so I would like DockCheck to download the image updates, then I can just run my Docker Compose command that will rebuild the containers with the new images. Then it'll only rebuild the ones that have an update.

[mag37]

No dumb questions!
Currently whole stacks are only restarted if using -f option. (Force stack restart after update. Caution: restarts once for every updated container within stack.).

So only containers chosen to update will be restarted (to use the newly downloaded image) - the rest of the stack or other containers will not be restarted.

[mag37]

Oh that's how it would work with the -f flag (not pretty, I should rework that).

But it shouldn't restart the whole stack otherwise - I'll need to troubleshoot this it seems. Should restart the specifically updated container then move to the next one.

[mag37]

I need to set up a few more multi-container composes in my test environments - currently only had one with updates.
But I ran dockcheck.sh -apsx 10 (I only have compose-based containers,so dont use -r ).

The container that got updated was a nginx-image in a compose file that has nginx+mariadb.
Only nginx had a image update and only nginx got recreated/restarted.

I will keep testing this.

[rbrussell82]

I'll remove -r and test when I have more updates. All of mine should be compose-based too.

[rbrussell82]

I found my problem. I had labels on my containers and had your restart-stack label set to true. Even though I wasn't using -l, it was still seeing the label and restarting all the containers that had the label set.

I removed the labels and now it only restarted the container with an update.

[mag37]

Ah great, glad you found the culprit!