IssueRaiser

[ECR] [console multi-arch support]: Support viewing multi-architecture images in the ECR Console UI correctly

<!-- Please keep this note for the community --> ### Community Note * Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request * Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request * If you are interested in working on this issue or have submitted a pull request, please leave a comment <!-- Thank you for keeping this note for the community --> <!-- **Security disclosures** If you think you’ve found a potential security issue, please do not post it in the Issues. Instead, please follow the instructions [here](https://aws.amazon.com/security/vulnerability-reporting/) or [email AWS security directly](mailto:aws-security@amazon.com). --> **Tell us about your request** Currently, if I were to push a multiple architecture build to ECR, it would show up in the console as multiple images. Let's say I pushed an image that was built for `linux/amd64` and `linux/arm64` and tagged it as "latest", three different images would show up in ECR 1. the digest for linux/amd64 showing as `<untagged>` 2. the digest for linux/arm64 showing as `<untagged>` 3. The digest that points to the manifest that points to the images in 1/2 showing as `latest` This is the correct behavior and pulling and interacting with these images via the `docker` CLI

Posted by bencooper222 on Dec 8, 2021, 10:31 PM

Tags

Related issues

Raise real-world problems, find people facing the same issue, and discuss solutions.3,000 issues0 comments

ux (Sysadmin)

[ECR] [console multi-arch support]: Support viewing multi-architecture images in the ECR Console UI correctly

bencooper222Dec 8, 2021, 10:31 PM

<!-- Please keep this note for the community --> ### Community Note * Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request * Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request * If you are interested in working on this issue or have submitted a pull request, please leave a comment <!-- Thank you for keeping this note for the community --> <!-- **Security disclosures** If you think you’ve found a potential security issue, please do not post it in the Issues. Instead, please follow the instructions [here](https://aws.amazon.com/security/vulnerability-reporting/) or [email AWS security directly](mailto:aws-security@amazon.com). --> **Tell us about your request** Currently, if I were to push a multiple architecture build to ECR, it would show up in the console as multiple images. Let's say I pushed an image that was built for `linux/amd64` and `linux/arm64` and tagged it as "latest", three different images would show up in ECR 1. the digest for linux/amd64 showing as `<untagged>` 2. the digest for linux/arm64 showing as `<untagged>` 3. The digest that points to the manifest that points to the images in 1/2 showing as `latest` This is the correct behavior and pulling and interacting with these images via the `docker` CLI

Comments (0)

No comments yet. Start the discussion.

Comment on this issue