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>
16 lines
529 B
Go
16 lines
529 B
Go
// +build experimental
|
|
|
|
package distribution
|
|
|
|
import "errors"
|
|
|
|
// ErrUnSupportedRegistry indicates that the registry does not support v2 protocol
|
|
var ErrUnSupportedRegistry = errors.New("Only V2 repositories are supported for plugin distribution")
|
|
|
|
// Plugin related media types
|
|
const (
|
|
MediaTypeManifest = "application/vnd.docker.distribution.manifest.v2+json"
|
|
MediaTypeConfig = "application/vnd.docker.plugin.v0+json"
|
|
MediaTypeLayer = "application/vnd.docker.image.rootfs.diff.tar.gzip"
|
|
DefaultTag = "latest"
|
|
)
|