On 01/23/2017 08:47 PM, Dominique Leuenberger / DimStar wrote:
On Fri, 2017-01-20 at 12:02 +0100, Jordi Massaguer Pla wrote:
Hi packagers,
I am packaging docker and we have this problem that if a user runs an unattended update, docker gets updated and so restarted. However, this is causing downtime issues on their services which are inside containers.
Should we not restart docker when installing? I think you should, but am I wrong?
Packages that KNOW that they case very negative effects on restart (e.g. dbus, the X server, PackageKit) can export this variable in their post script just before executing the service handling macros. But for docker, where the issue is 'only' downtime, I'd argue it is up to the admin to decide if he wants to skip the restart (by setting the corresponding variables in his system) - and thus take care of actually enabling the new services, or not (follow the default, restart the service up update)
In http://bugzilla.suse.com/show_bug.cgi?id=980555 it was decided that as migrations can take many hours in this case the service shouldn't be automatically restarted. (When docker isn't doing a migration it should be). -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B