[Fargate] [request]: Lazily load container images with SOCI from 3rd party registries
- Dominant language
- Shell
- Stars
- 5.4k
- Forks
- 334
- PR merge metrics
- No merged PRs in 30d
Description
### 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
**Tell us about your request**
Lazy loading container images with SOCI on AWS Fargate only supports container images stored in a private ECR repository. [SOCI has been tested on a range of other registries](https://github.com/awslabs/soci-snapshotter/blob/main/docs/registry.md), it would be good if you can use these other registries with Fargate Tasks.
**Which service(s) is this request for?**
Fargate
**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
Lazy Load container images from other container registries on AWS Fargate.
**Are you currently working around this issue?**
Store a copy of all container images in ECR.
**Additional context**
**Attachments**
Contributor guide
Research direction
No repository files, tests, or entry points are identified in the request. Start with the linked SOCI registry documentation and the Fargate request details; done would require defined support for lazily loading images from the tested third-party registries without copying them into ECR.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- cloud
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100