Looking at the docker stack documentation:

Extended description

 

Create and update a stack from a compose or a dab file on the swarm

From this blog article: docker stack works in a similar way as docker compose. It’s idempotent. If the stack is already deployed, docker stack deploy will restart only those services which has the digest or tag that is updated:

From my experience, when I deploy the same stack again with one service changing, only the updated service will be restarted.

BUT... there seems to be some limitations to changes that are taken into account (some report bugs with image tags), so give it a try and see if works as expected.

You can also use service update if you want to be sure that only targeted service if updated with your changes.

You can also refer to this similar SO QA.

Looking at the docker stack documentation:

Extended description

Create and update a stack from a compose or a dab file on the swarm

From this blog article: docker stack works in a similar way as docker compose. It’s idempotent. If the stack is already deployed, docker stack deploy will restart only those services which has the digest or tag that is updated:

From my experience, when I deploy the same stack again with one service changing, only the updated service will be restarted.

BUT... there seems to be some limitations to changes that are taken into account (some report bugs with image tags), so give it a try and see if works as expected.

You can also use service update if you want to be sure that only targeted service if updated with your changes.

You can also refer to this similar SO QA.

Looking at the docker stack documentation:

Extended description

Create and update a stack from a compose or a dab file on the swarm

So docker stack works in a similar way as Docker Compose. It’s idempotent. You can run it as many times as you like and the result will always be the same.

From my experience, when I deploy the same stack again with one service changing, only the updated service will be restarted.

BUT... there seems to be some limitations to changes that are taken into account (some report bugs with image tags), so give it a try and see if works as expected.

You can also use service update if you want to be sure that only targeted service if updated with your changes.

You can also refer to this similar SO QA

Looking at the docker stack documentation:

Extended description

Create and update a stack from a compose or a dab file on the swarm

From this blog article: docker stack works in a similar way as docker compose. It’s idempotent. If the stack is already deployed, docker stack deploy will restart only those services which has the digest or tag that is updated:

From my experience, when I deploy the same stack again with one service changing, only the updated service will be restarted.

BUT... there seems to be some limitations to changes that are taken into account (some report bugs with image tags), so give it a try and see if works as expected.

You can also use service update if you want to be sure that only targeted service if updated with your changes.

You can also refer to this similar SO QA.