go.mod: change imports to github.com/distribution/distribution/v3

Go 1.13 and up enforce import paths to be versioned if a project
contains a go.mod and has released v2 or up.

The current v2.x branches (and releases) do not yet have a go.mod,
and therefore are still allowed to be imported with a non-versioned
import path (go modules add a `+incompatible` annotation in that case).

However, now that this project has a `go.mod` file, incompatible
import paths will not be accepted by go modules, and attempting
to use code from this repository will fail.

This patch uses `v3` for the import-paths (not `v2`), because changing
import paths itself is a breaking change, which means that  the
next release should increment the "major" version to comply with
SemVer (as go modules dictate).

Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
This commit is contained in:
Sebastiaan van Stijn 2020-08-24 13:18:39 +02:00
parent 6200038bc7
commit 1d33874951
No known key found for this signature in database
GPG key ID: 76698F39D527CE8C
173 changed files with 527 additions and 527 deletions

View file

@ -55,7 +55,7 @@ $ docker run -d -p 5000:5000 --restart=always --name registry \
```
Use this
[example YAML file](https://github.com/docker/distribution/blob/master/cmd/registry/config-example.yml)
[example YAML file](https://github.com/distribution/distribution/blob/master/cmd/registry/config-example.yml)
as a starting point.
## List of configuration options
@ -1206,7 +1206,7 @@ This example configures the registry instance to run on port `5000`, binding to
verbose.
See
[config-example.yml](https://github.com/docker/distribution/blob/master/cmd/registry/config-example.yml)
[config-example.yml](https://github.com/distribution/distribution/blob/master/cmd/registry/config-example.yml)
for another simple configuration. Both examples are generally useful for local
development.

View file

@ -6,9 +6,9 @@ keywords: registry, on-prem, images, tags, repository, distribution, JWT authent
# Docker Registry v2 Bearer token specification
This specification covers the `docker/distribution` implementation of the
This specification covers the `distribution/distribution` implementation of the
v2 Registry's authentication schema. Specifically, it describes the JSON
Web Token schema that `docker/distribution` has adopted to implement the
Web Token schema that `distribution/distribution` has adopted to implement the
client-opaque Bearer token issued by an authentication service and
understood by the registry.

View file

@ -100,7 +100,7 @@ alpha-numeric := /[a-z0-9]+/
separator := /[_.]|__|[-]*/
```
Full reference grammar is defined
[here](https://godoc.org/github.com/docker/distribution/reference). Currently
[here](https://godoc.org/github.com/distribution/distribution/reference). Currently
the scope name grammar is a subset of the reference grammar.
> **NOTE:** that the `resourcename` may contain one `:` due to a possible port

View file

@ -6,7 +6,7 @@ published: false
This is a list of known implementations of the Distribution API spec.
## [Docker Distribution Registry](https://github.com/docker/distribution)
## [Docker Distribution Registry](https://github.com/distribution/distribution)
Docker distribution is the reference implementation of the distribution API
specification. It aims to fully implement the entire specification.

View file

@ -12,7 +12,7 @@ release](https://github.com/docker/docker/commit/9f482a66ab37ec396ac61ed0c00d591
It is a provisional manifest to provide a compatibility with the [V1 Image
format](https://github.com/docker/docker/blob/master/image/spec/v1.md), as the
requirements are defined for the [V2 Schema 2
image](https://github.com/docker/distribution/pull/62).
image](https://github.com/distribution/distribution/pull/62).
Image manifests describe the various constituents of a docker image. Image