Skip to content
  1. Jul 17, 2017
  2. Jul 07, 2017
  3. Jul 06, 2017
  4. Jul 05, 2017
  5. Jul 04, 2017
  6. Jul 03, 2017
  7. Jun 30, 2017
  8. Jun 29, 2017
  9. Jun 27, 2017
  10. Jun 26, 2017
  11. Jun 23, 2017
  12. Jun 20, 2017
  13. Jun 19, 2017
  14. Jun 16, 2017
  15. Jun 14, 2017
  16. Jun 12, 2017
  17. Jun 09, 2017
  18. Jun 08, 2017
  19. May 31, 2017
  20. May 27, 2017
  21. May 25, 2017
  22. May 23, 2017
  23. May 19, 2017
  24. May 17, 2017
    • Josh Lothian's avatar
      Leave 'live-restore' false · 6f67367b
      Josh Lothian authored
      Leave live-restore false to updates always pick
      up new network configuration
      6f67367b
    • Josh Lothian's avatar
      Update handler names and explanation · 9ee0600a
      Josh Lothian authored
      9ee0600a
    • Josh Lothian's avatar
      Reconfigure docker restart behavior on atomic · 30cc7c84
      Josh Lothian authored
      Before restarting docker, instruct it to kill running
      containers when it restarts.
      
      Needs a second docker restart after we restore the original
      behavior, otherwise the next time docker is restarted by
      an operator, it will unexpectedly bring down all running
      containers.
      30cc7c84
    • Josh Lothian's avatar
      Fix docker restart in atomic · a5bb24b8
      Josh Lothian authored
      In atomic, containers are left running when docker is restarted.
      When docker is restarted after the flannel config is put in place,
      the docker0 interface isn't re-IPed because docker sees the running
      containers and won't update the previous config.
      
      This patch kills all the running containers after docker is stopped.
      We can't simply `docker stop` the running containers, as they respawn
      before we've got a chance to stop the docker daemon, so we need to
      use runc to do this after dockerd is stopped.
      a5bb24b8
Loading