Comment 10 for bug 1906364

Thanks @bryce for the detailed updates.

For us personally its the second time we run into a docker daemon restart on production (including all container restarts).

The only reason why this time it got much more attention is that a bug prevented a clean restart of the daemon, leaving containers offline.

This fact tells us that most of the people never noticed that their containers were also during the last update restartet. (Which is fine because mostly a short restart, for example of a webserver nobody would notice)

This is also fine of most of our servers because they running lightweight containers.

The only reason why we noticed it (this and last time) is that we running heavy database containers (for example elasticsearch with couple of TBs) which have a restart time of minutes instead of seconds.

Especially its critical (and loosing consistency) when containers of the same kind get restarted at the same time.

All of this chain is triggered by the unattended updates. Thats why we excluded the automatic updates for the docker package.

But this doesnt help if depending package updates still restarting the docker daemon/containers.

Since the unattended package is still marked as 'wont-fix', and the dependencies problem is explained above..

The only way to safely prevent docker daemon restarts is to fully disable the whole unattended updates? Can someone confirm this?