reference

reference copied to clipboard

- relates to https://github.com/distribution/reference/pull/12

thaJeztah

Parsing images with digest is not clear

1

Parsing images with digest like `docker.io/library/nginx@sha256:ed6d2c43c8fbcd3eaa44c9dab6d94cb346234476230dc1681227aa72d07181ee` using `Parse` doesn't work without having blank imports for a package that registers hash functions, for example having something like `import _ "crypto/sha256"`. `go-digest`...

AbdelrahmanElawady

parsing breaks with IPv4-mapped IPv6 addresses

3

The [IPv6 address syntax](https://en.wikipedia.org/wiki/IPv6_address) allows forms such as `::ffff:192.0.2.128`, but the reference parsing code, despite allowing other forms of IPv6 address, doesn't seem to allow these, even though the Go...

rogpeppe

Repository name regex is outdated [docs].

7

Please update the regex mentioned in docs because it is outdated. https://docs.docker.com/registry/spec/api/#overview ``` A repository name is broken up into path components. A component of a repository name must be...

ipanova

use sync.OnceValue for various regular expressions, require go1.21

7

- [x] depends on https://github.com/distribution/reference/pull/16 ---- ### use sync.OnceValue for various regular expressions, require go1.21 Using regex.MustCompile consumes a significant amount of memory when importing the package, even if those...

thaJeztah

I understand that `reference.Named` may not contains the domain part according to its implementation. However, the function [`ParseNamed(s string) (Named, error)`](https://github.com/distribution/distribution/blob/ede90db01c18cc8c3148e227b7242ac3efba370b/reference/reference.go#L242) requires given `s` to be canonical which conatins the...

lesomnus

When reference.Parse returns a digest only ref?

5

I cannot see the test case in https://github.com/distribution/reference/blob/v0.6.0/reference_test.go#L14 It seems all are `Named`.

liubog2008