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>
This commit is contained in:
parent
b0b3249bc2
commit
36cf93fb0c
3 changed files with 11 additions and 1 deletions
|
@ -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).
|
||||
|
|
3
pkg/plugins/discovery_unix.go
Normal file
3
pkg/plugins/discovery_unix.go
Normal file
|
@ -0,0 +1,3 @@
|
|||
package plugins
|
||||
|
||||
var specsPaths = []string{"/etc/docker/plugins", "/usr/lib/docker/plugins"}
|
8
pkg/plugins/discovery_windows.go
Normal file
8
pkg/plugins/discovery_windows.go
Normal file
|
@ -0,0 +1,8 @@
|
|||
package plugins
|
||||
|
||||
import (
|
||||
"os"
|
||||
"path/filepath"
|
||||
)
|
||||
|
||||
var specPaths = []string{filepath.Join(os.Getenv("programdata"), "docker", "plugins")}
|
Loading…
Reference in a new issue