Milos Gajdos

Dupe of https://github.com/distribution/distribution/issues/3725

There is no such thing at the moment no. You can set up a lifecycle policy in S3 though, be careful so the deleted data don't break the integrity of...

This is a complicated problem @dextercrypt ...you need to make sure you won't break the integrity of the content stored in registry so the S3 lifecycle policy can really help...

> The reason I am afraid to put a lifecycle on this is that once it breaks the Layer files of the Registry, I fear that my registry would get...

All Docker Official Images are available on ECR Public https://gallery.ecr.aws/docker/library/registry but ECR still doesnt seem to support IPv6. Maybe if more interested is expressed in https://github.com/aws/containers-roadmap/issues/2287 it could get prioritised

Always use cache: https://distribution.github.io/distribution/about/configuration/#cache Also, please avoid using `v2.8.x` release and use the latest available `v3` release.

> So it looks like there is a mix of custom and oauth protocols in use. I don't think that's the case, though I can't speak on behalf of `moby`...

Please use `v3` images. `v2` is in a state that's not been touched for a long time.

They just merged https://github.com/docker-library/official-images/pull/17151 Not sure how long it takes to build it 🤷‍♂️ In the meantime you can grab the latest release from: * https://hub.docker.com/r/distribution/distribution/tags (docker pull distribution/distribution:3.0.0-beta.1) *...

Unfortunately, the latest alpine image we build off has those vulns so there is nothing we can do about that until that basee image is fixed. https://hub.docker.com/_/alpine/tags Grab a binary...