How do I resolve the "Image does not exist" error when my tasks fail to start in my Amazon ECS cluster?

Short description

You receive this error when you pull images from an Amazon Elastic Container Registry (Amazon ECR) private repository.

If you didn't receive this error message, then choose one of the following resolutions for your issue or error message:

• Your container exits because of application issues or resource constraints. To resolve this issue, see How do I troubleshoot Amazon ECS tasks that stop or fail to start while my container exits?
• The health checks for your Application Load Balancer are failing. To resolve this issue, see How can I get my Amazon ECS tasks that use the Amazon EC2 launch type to pass the Application Load Balancer health check?
• Docker can't pull the container image. To resolve this issue, see CannotPullContainer task errors in Amazon ECS.
• You get an error message similar to the following: "[AWS service] was unable to place a task because no container instance met all of its requirements". For resolve this issue, see How do I resolve the "[AWS service] was unable to place a task because no container instance met all of its requirements" error in Amazon ECS?
• You get an error message similar to the following: "[AWS service] was unable to place a task because no container instance met all of its requirements. The closest matching container-instance container-instance-id has insufficient CPU units available". To resolve this issue, see How do I resolve "the closest matching container-instance container-instance-id has insufficient CPU units available" error in Amazon ECS?
• You get an error message similar to the following: "[AWS service] was unable to place a task because no container instance met all of its requirements. The closest matching container-instance container-instance-id encountered error "AGENT". To resolve this issue, see How do I resolve "the closest matching container-instance container-instance-id encountered error 'AGENT'" error for my service in Amazon ECS?

Note: To troubleshoot Amazon ECS service issues, check for diagnostic information in the service event log.

Resolution

Note: If you receive errors when you run AWS Command Line Interface (AWS CLI) commands, then see Troubleshoot AWS CLI errors. Also, make sure that you're using the most recent AWS CLI version.

To resolve the Image does not exist error, complete the following steps:

1. Verify that the image is declared in your Amazon ECS task definition. For more information, see Image.
2. Verify that the Docker image exists in the Amazon ECR repository. For more information, see Viewing image details in Amazon ECR. To view repository information, use the Amazon ECR console. Or, run the following commands.
   To confirm that an image exists in an ECR repository, run the list-images command:

   aws ecr list-images --repository-name "hello-world"  --region us-east-1

   To filter for images in an ECR repository, run the describe-images command:

   aws ecr describe-images --repository-name "hello-world" --region us-east-1 --query 'sort_by(imageDetails,& imagePushedAt)[*]'

   Note: Replace repository-name and region with your values.
3. Specify an Amazon ECR image in your task definition. Use the full URI for the image. For more information, see Amazon ECR image and task definition IAM role.
   Important: Verify that there are no leading or trailing character spaces in the URI for the image.

Related information

Private images in Amazon ECR