Steve Litt writes:

> On Fri, 09 Nov 2018 22:13:16 +0900
> Olaf Meeuwissen <paddy-hack@???> wrote:
>
>> [ ... docker-ce upgrade fails to restart daemon on Devuan ... ]
>> [ ... same upgrade restarted daemon just fine on Debian ... ]
>> [ ... suspecting docker-ce to only cater to systemd ... ]

For the record, the approximately monthly upgrades of docker-ce have
been smooth sailing since 17.10 or thereabouts. This is the first time
I observed trouble.

> This kind of thing is exactly why I started running daemontools on top
> of sysvinit. I found that for some things, sysvinit was just to
> complicated to easily troubleshoot.
>
> Nobody uses daemontools anymore. They use runit (with the sysvinit
> pID1) instead.

When upgrading a package that provides a daemon, I expect the upgrade to
shut down the daemon provided by the old version and start the one from
the new version. I do not want anything to "muck" with that, be that
daemontools or anything else.
Keeping an otherwise running daemon running is a different story.

I checked to /var/lib/dpkg/info/docker-ce.{prerm,postinst} scripts. For
18.06.1~ce~3-0~debian these include calls to invoke-rc.d to stop and
start the daemon. As of 5:18.09.0~3-0~debian-stretch these calls are
gone. The only stop/start mechanism supported is systemd :-(
Ditto for containerd.io :-(

FWIW, I've submitted https://github.com/docker/for-linux/issues/482

Hope this helps,
--
Olaf Meeuwissen, LPIC-2            FSF Associate Member since 2004-01-27
 GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13  F43E B8A4 A88A F84A 2DD9
 Support Free Software                        https://my.fsf.org/donate
 Join the Free Software Foundation              https://my.fsf.org/join