On Sat, 25 Oct 2014 15:08:05 -0600 Tianon Gravi <admwig...@gmail.com> wrote: > On 23 October 2014 01:05, Joey Hess <jo...@debian.org> wrote: > > Maybe --restart=always or --restart=on-error is needed to get the old > > behavior? I cannot make much sense of the upstream changelog. > > You've interpreted it correctly here. Upstream decided that it was > better to add an explicit "restart policy" for each container than to > continue to maintain their fragile heuristics for when a container is > deemed appropriate to automatically restart (since it didn't actually > work correctly half the time anyways).
Tianon, reading the docs at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766438 I don't think your explanation applies to this particular case # quote Using the --restart flag on Docker run you can specify a restart policy for how a container should or should not be restarted on exit. no - Do not restart the container when it exits. on-failure - Restart the container only if it exits with a non zero exit status. always - Always restart the container regardless of the exit status. You can also specify the maximum amount of times Docker will try to restart the container when using the on-failure policy. The default is that Docker will try forever to restart the container. # endquote My understanding of this excerpt is that containers that exit by themselves (e.g. due to a failure) are restarted according to the restart policy. It does not seem to apply to containers that were stopped by docker itself before the system was shutdown or rebooted. Michael -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
