Tianon Gravi

`distribution/registry` is likely a Docker Hub "Automated Build" of https://github.com/docker/distribution/blob/master/Dockerfile, so you're likely to get the latest and greatest development improvements from `master` by using that image (assuming it's still...

I'd personally rather see these pre-compiled artifacts move to be official release artifacts attached to https://github.com/docker/distribution/releases/tag/v2.7.1, especially since that has broader usefulness outside of folks running the `registry` official image...

> > invalid platform architecture "aarch64". > > Looks like the image is reporting the incorrect platform. > > @tianon Any ideas here? This specific error looks more to me...

Once this is merged, that'd be a PR to https://github.com/docker-library/official-images/blob/master/library/registry, which I'd be happy to make for you if you'd like. :+1:

(Probably worth considering whether 2.5.x is still actually supported and update to the new RFC 2822-based format while we're at it.)

Representing just one downstream, I don't have any problem with a rename here (I'll just adjust to match :+1:), but I know it's extremely unlikely that I'm the only one...

(I don't think a "transition release" with both really helps much though -- most affected users won't necessarily even notice the duplication and so it'll just delay the adjustment they...

Does a more obvious value for "REGISTRY_AUTH" like "no" or "none" also work?

That's kind of a poor user experience. :disappointed: Any chance that could be updated to also allow `no` or `none`? IMO, `-e REGISTRY_AUTH=none` is a _lot_ easier to read and...

If this is something y'all want to move forward with, it should be reasonably safe to do so (assuming the docs are also updated, which currently assume the default will...