severity 832103 important thanks On 31 August 2016 at 12:02, Felipe Sateler <fsate...@debian.org> wrote: > 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.
Yeah, I haven't been able to dig into exactly what the mismatch is, but I've found that even on my Gentoo machine, even just recompiling the exact same version of containerd/runc (which often leads to the same set of bits, even!) without restarting Docker can cause container starting issues (so even if we did restart Docker during upgrade, it wouldn't restart Docker during containerd/runc upgrade and we'd be hosed again, especially since Docker runs its own instance of containerd). I don't think there's really much we (Debian) can do here besides adding a note in README.Debian (do folks generally read that?), and as such I've decreased the severity of this report. ♥, - Tianon 4096R / B42F 6819 007F 00F8 8E36 4FD4 036A 9C25 BF35 7DD4
