Add spec file support for Windows plugin discovery.

Plugin discovery on Windows is not possible using named pipes. However,
it is possible using spec file (tcp based). This adds Windows specific
paths for discovery.

Fixes #23605

Signed-off-by: Anusha Ragunathan <anusha@docker.com>
Upstream-commit: 36cf93fb0c45ce62b3cb1e82e1ecae1486017c9b
Component: engine
This commit is contained in:
Anusha Ragunathan
2016-08-19 18:01:14 -07:00
parent 92992ea84a
commit cb628977aa
3 changed files with 11 additions and 1 deletions

View File

@ -16,7 +16,6 @@ var (
// ErrNotFound plugin not found
ErrNotFound = errors.New("plugin not found")
socketsPath = "/run/docker/plugins"
specsPaths = []string{"/etc/docker/plugins", "/usr/lib/docker/plugins"}
)
// localRegistry defines a registry that is local (using unix socket).

View File

@ -0,0 +1,3 @@
package plugins
var specsPaths = []string{"/etc/docker/plugins", "/usr/lib/docker/plugins"}

View File

@ -0,0 +1,8 @@
package plugins
import (
"os"
"path/filepath"
)
var specPaths = []string{filepath.Join(os.Getenv("programdata"), "docker", "plugins")}