7568d41513
During daemon startup, all containers are registered before any are started. During container registration it was calling out to initialize volumes. If the volume uses a plugin that is running in a container, this will cause the restart of that container to fail since the plugin is not yet running. This also slowed down daemon startup since volume initialization was happening sequentially, which can be slow (and is flat out slow since initialization would fail but take 8 seconds for each volume to do it). This fix holds off on volume initialization until after containers are restarted and does the initialization in parallel. The containers that are restarted will have thier volumes initialized because they are being started. If any of these containers are using a plugin they will just keep retrying to reach the plugin (up to the timeout, which is 8seconds) until the container with the plugin is up and running. Signed-off-by: Brian Goff <cpuguy83@gmail.com> Upstream-commit: d85b9f858050dbfb2dde3d68517952958b8e38ee Component: engine