This is a design flaw and upstream gave up on the idea of restarting containers on upgrade.
Docker's upgrade tip from 17.12.1 release notes states is clearly:
"You must stop all containers and plugins BEFORE upgrading"
https://github.com/docker/docker-ce/releases/tag/v17.12.1-ce
If that's a problem then using superior container runtime such as "rkt" might
be a solution since "rkt" is not a daemon and its upgrade don't interfere
with running containers.
--
Best wishes,
Dmitry Smirnov
---
There is no society in human history that ever suffered because its people
became too reasonable.
-- Sam Harris
signature.asc
Description: This is a digitally signed message part.
