I have some drone CI/CD builders running.
I’d like to be able to do a rolling update, and I have sorta accomplished that by adding
So far so good - The droner runner container receives the shutdown signal, stops picking up new jobs and exits once its current are done. Meanwhile a new updated container becomes available and starts picking up new jobs.
However, while this works fine for most of our stuff, but a few instances we only want one running at a time.
I’ve tried adding this to my service:
deploy: replicas: 1 placement: max_replicas_per_node: 1 update_config: order: stop-first
However, docker swarm seems to ignore it.
I will still have two instances running on the same node during a rolling update. I get how max replicas per node might not do the job, but do I also misunderstand how stop-first works?