Finally have time to look into your suggestions. Hopefully you check your comments every once in a while... > Are you sure the Docker Image digest did not chan

Finally have time to look into your suggestions. Hopefully you check your comments every once in a while... > Are you sure the Docker Image digest did not change? Have you tried pinning an actual Docker Image digest? Mostly sure. Many of my tests only changed the docker-compose file, not the actual image. So even though GitLab was rebuilding the image, the image digest would not have changed. I'll try to find time to pin the digest just to double check, though. > Is this true even with "oder: stop-first"? Er, did you mean "order"? I only see `--update-order` as a flag on the `docker service update` command. I do not see it in the docker-compose specification. So far all my tests have been through Portainer's stack deployment feature. So all changes are in my docker-compose file. Maybe it would just work if I stuck it in the deploy.update section? I'll try. > True, but there are still some volume plugins that work around and local storage should work if you use labels to pin the replicas to nodes. I have tried pinning specific services to specific nodes to make local storage work. And I've use labels to force only one replica per node when using replicas. What volume plugins are you thinking of? I haven't found any that seem to be maintained outside of local storage and nfs. And maybe some that would work if I were in some cloud host... Anyway, thanks for giving me a couple things to try. :)