[ECS][Request]: improve description when Docker Image is not Found
- 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**
This feature request (to provide greater clarity when a Docker image is not available) is a UX improvement that will aid issue diagnosis and give the ECS product a more finished feel.
**Which service(s) is this request for?**
ECS Fargate, possibly ECS.
**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
The issue I'm trying to solve is that the error message provided when a Docker Image is not available is not likely to be understood by an ECS user.
**Are you currently working around this issue?**
Institutional knowledge.
**Additional context**
Obviously, I made a mistake by trying to launch the `latest:latest` image but the error message `"InternalError: failed to create container model: failed to normalize image reference"` is not going to be understood by anyone. If you search for this phrase (`failed to normalize image reference`) on the Internet you'll see a number of posts.
If you wanted to _really_ have a good user experience you could link to a troubleshooting document or state clearly "the image tag ${image_tag} does not exist in the specified repository".
**Attachments**
Contributor guide
Research direction
Start with the issue's ECS Fargate example and the reported “failed to normalize image reference” error; this roadmap repository names no source files or tests. Determine the expected behavior for an unavailable Docker image, and consider the work complete when ECS presents a clear, actionable message or troubleshooting reference to users.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, docker
- Domain
- cloud
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100