f37117045c
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>
32 lines
1,003 B
Go
32 lines
1,003 B
Go
// +build experimental
|
|
|
|
package graphdriver
|
|
|
|
import (
|
|
"fmt"
|
|
"io"
|
|
|
|
"github.com/docker/docker/pkg/plugins"
|
|
)
|
|
|
|
type pluginClient interface {
|
|
// Call calls the specified method with the specified arguments for the plugin.
|
|
Call(string, interface{}, interface{}) error
|
|
// Stream calls the specified method with the specified arguments for the plugin and returns the response IO stream
|
|
Stream(string, interface{}) (io.ReadCloser, error)
|
|
// SendFile calls the specified method, and passes through the IO stream
|
|
SendFile(string, io.Reader, interface{}) error
|
|
}
|
|
|
|
func lookupPlugin(name, home string, opts []string) (Driver, error) {
|
|
pl, err := plugins.Get(name, "GraphDriver")
|
|
if err != nil {
|
|
return nil, fmt.Errorf("Error looking up graphdriver plugin %s: %v", name, err)
|
|
}
|
|
return newPluginDriver(name, home, opts, pl.Client())
|
|
}
|
|
|
|
func newPluginDriver(name, home string, opts []string, c pluginClient) (Driver, error) {
|
|
proxy := &graphDriverProxy{name, c}
|
|
return proxy, proxy.Init(home, opts)
|
|
}
|