moby--moby/plugin/distribution/types.go

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")

// ErrUnsupportedMediaType indicates we are pulling content that's not a plugin
var ErrUnsupportedMediaType = errors.New("content is not a plugin")

// DefaultTag is the default tag for plugins
const DefaultTag = "latest"
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-05-16 11:50:55 -04:00			`package distribution`

			`import "errors"`

Detect non-plugin content during install and error out. Signed-off-by: Anusha Ragunathan <anusha@docker.com> 2016-07-06 15:16:14 -04:00			`// ErrUnsupportedRegistry indicates that the registry does not support v2 protocol`
			`var ErrUnsupportedRegistry = errors.New("only V2 repositories are supported for plugin distribution")`

			`// ErrUnsupportedMediaType indicates we are pulling content that's not a plugin`
			`var ErrUnsupportedMediaType = errors.New("content is not a plugin")`
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-05-16 11:50:55 -04:00
Make `docker pull` detect plugin content and error out. Signed-off-by: Anusha Ragunathan <anusha@docker.com> 2016-08-10 15:04:42 -04:00			`// DefaultTag is the default tag for plugins`
			`const DefaultTag = "latest"`