Le 05/07/18 à 10:38, Dmitry Smirnov a écrit :
On Thursday, 5 July 2018 5:57:43 PM AEST Laurent Bigonville wrote:
Since the last upload, docker.io Recommends the needrestart package,
that means that the package is installed almost everywhere.
This is how I intended it to be.
You also have checkrestart that is way less aggressive but that needs to
be run by hand after an update.
I believe that lot of administrator would prefer that solution
But needrestart changes the behaviour of the upgrade by interractively
asking to restart the daemons after the upgrade.
Isn't that a bit too agressive? Shouldn't needrestart be downgraded to a
Suggests?
No, I'd rather keep it as-is...
Docker is a very ugly package in regards to restart on upgrade.
There is no elegant solution to this and it seems that the best of all
options is to prompt user about daemon restart on upgrade.
Without prompt it is either to kill all running containers on upgrade (when
daemon is restarted) or lose control of Docker due to API mismatch between
CLI and the daemon (when daemon is not restarted). See #792327, #786724.
These days unattended-upgrades package is installed by default, and if
I'm understanding properly in this case needrestart will just list the
packages that needs to be restarted an nothing else.
The problem you are mentioning will persist.
IMHO using "needrestart" is a best way to prompt for daemon restart on Docker
upgrade so I very much meant to put "needrestart" to Recommends.
It is unfortunate if there are any side effects but perhaps they can be
addressed in "needrestart"?
