Difference between revisions of "No Container Instances were found in your cluster"
Jump to navigation
Jump to search
(Created page with "service your_service was unable to place a task because no container instance met all of its requirements. Reason: No Container Instances were found in your cluster. For m...") |
|||
| Line 1: | Line 1: | ||
| − | service your_service [[was unable to place a task because no container instance met all of its requirements]]. Reason: No Container Instances were found in your cluster. For more information, see the Troubleshooting section of the [[Amazon ECS Developer Guide]]. | + | service your_service [[was unable to place a task because no container instance met all of its requirements]]. Reason: No Container Instances were found in your cluster. For more information, see the Troubleshooting section of the [[Amazon ECS Developer Guide]]. |
| + | |||
| + | [[No container instances were found in your capacity provider]] | ||
{{ECS}} | {{ECS}} | ||
Revision as of 13:53, 24 April 2023
service your_service was unable to place a task because no container instance met all of its requirements. Reason: No Container Instances were found in your cluster. For more information, see the Troubleshooting section of the Amazon ECS Developer Guide.
No container instances were found in your capacity provider
Amazon ECS, Service, Tasks (Task overview), capacity providers, Cluster Auto Scaling (CAS), aws ecs, ecs-cli, ~/.ecs/config, AWS Copilot, AWS Fargate, AWS CloudWatch Container Insights, /etc/ecs/ecs.config, Security group (SG), container agent, task definition, Amazon ECS events, best practices, Amazon ECS Exec Checker, Amazon ECS Agent, Service Connect, AWSServiceRoleForECS, Terraform ECS
Advertising:
