4 Commits

Author	SHA1	Message	Date
Victor Vieux	5cc103e9e9	fix plugin restart on docker restart ... Signed-off-by: Victor Vieux <vieux@docker.com> (cherry picked from commit ab12ed4a5642edb4d96b54b6152f12260093f3ea) Signed-off-by: Tibor Vass <tibor@docker.com>	2016-08-11 17:56:49 -07:00
Anusha Ragunathan	db94be5084	Shutdown plugins during daemon shutdown. ... Signed-off-by: Anusha Ragunathan <anusha@docker.com> (cherry picked from commit 863ab9ab134d0baef3c7e5d745eded891e87e734) Signed-off-by: Tibor Vass <tibor@docker.com>	2016-07-12 15:50:21 -07:00
Brian Goff	9647e4d6cc	Implement plugin restore after daemon restart ... This ensures that: - The in-memory plugin store is populated with all the plugins - Plugins which were active before daemon restart are active after. This utilizes the liverestore feature when available, otherwise it manually starts the plugin. Signed-off-by: Brian Goff <cpuguy83@gmail.com> (cherry picked from commit dfd91873056c172ffc061d882da0cd18204b521a)	2016-06-16 23:36:58 -07:00
Tibor Vass	f37117045c	plugins: experimental support for new plugin management ... This patch introduces a new experimental engine-level plugin management with a new API and command line. Plugins can be distributed via a Docker registry, and their lifecycle is managed by the engine. This makes plugins a first-class construct. For more background, have a look at issue #20363. Documentation is in a separate commit. If you want to understand how the new plugin system works, you can start by reading the documentation. Note: backwards compatibility with existing plugins is maintained, albeit they won't benefit from the advantages of the new system. Signed-off-by: Tibor Vass <tibor@docker.com> Signed-off-by: Anusha Ragunathan <anusha@docker.com>	2016-06-14 14:20:27 -07:00