c4a861fdf5a4549ec4bc76b59876d2c5d0ced42d
When updates happen, the current behavior is to kill all running instances and dispatch new tasks. Common use cases for container updates involve small numbers of containers, meaning the app will go down on most updates. Setting parallelism to 1 ensures that at most one task will go down during the update. Services with higher replica counts can increase this number accordingly to meet their needs. Signed-off-by: Stephen J Day <stephen.day@docker.com> Upstream-commit: 67246afd3dbcb53fea470bd3e45578370207139d Component: engine
Description
No description provided
Languages
Go
92%
Shell
5.5%
Dockerfile
1.1%
Go-Checksums
0.9%
Makefile
0.3%
Other
0.2%