On 31 August 2016 at 11:55, Tianon Gravi <tia...@debian.org> wrote: > On 25 July 2016 at 07:42, Felipe Sateler <fsate...@debian.org> wrote: >> I had this problem too. Restarting the daemon seems to have fixed the >> issue. I think the docker daemon should be restarted on package >> upgrades, as most daemons do. > > Normally I would tend to agree, but in this case, restarting the > daemon means that we've force-killed all the user's running > containers, so I'm more on the fence about it.
Ack. Anyway, isn't this a condition docker can detect (mismatch between binaries and the running daemon)? In that case it could print a suitable help message for the user. -- Saludos, Felipe Sateler