ECR: support manifest lists

[jtoberon]

ECR should support manifest lists (https://docs.docker.com/registry/spec/manifest-v2-2/#manifest-list). This feature allows ECR customers to create and consume multi-architecture images more easily.

[FernandoMiguel]

I strongly support this. The amount of use cases we are blocked by the lack of manifest support when using cache images, is affecting so many developers

[jmeickle]

This lack of support is actually blocking us from adopting Buildkit, since it prevents properly caching in that scenario.

[EduardSergeev]

We had to switch to self-hosted registry:2 because we needed to store multi-arch images. Incidentally we needed it because we wanted to use AWS new A1 instances in production along with T3 instances in development.

[frzifus]

would be great to see that on the roadmap. 🥇

[diclophis]

This would be huge advantage for ECR to support buildkit pulling caching from the registry

[marksantoso]

Looking forward to this.

[omieomye]

This is rolling out now and ready to use in most regions. We'll publish a formal announcement shortly with some more reading. In the meantime, docs are updated and please let us know your feedback.

[nithinvenugopal]

Does AWS batch support multi-architecture compute environment in it's queue with this change?

[omieomye]

@nithinvenugopal I'll let you know.