ECS will not launch instance, “unable to place a task because the resources could not be found.”

I cannot figure out why my ecs service will not launch, and keep being given the error “service unable to place a task because the resources could not be found”.

In my task definition, I have 500 cpu units dedicated and 250 memory, for just a very small sample node app that’s just serving up my static assets.

  • Amazon ECS private DockerHub repo: Unable to decode provided docker credentials error
  • Deploying multiple Deis clusters
  • “Invalid configuration for registry” error when executing “eb local run”
  • Elastic Beanstalk with multiple environments and URL routing between them
  • AWS ECS running a task that requires many cores
  • Enterprise Apps with Docker and Elastic Beanstalk
  • I am launching my service with 1 task and no ELB.

  • docker behind proxy doesn't use system proxy info
  • How to pass parameters between Multiple containers using docker-compose
  • Why other unrelated processes are killed when one process is killed in docker container
  • Docker freezes even in a small setup
  • How to run Docker on Ubuntu 15.04?
  • Docker: Add a restart policy to a container that was already created
  • One Solution collect form web for “ECS will not launch instance, “unable to place a task because the resources could not be found.””

    my guess is that your cpu units is too high. https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task_definition_parameters.html#container_definition_environment

    it’s a harder metric to guess if you haven’t really measured it much on your app.

    anyway, i’m hitting a similar issue, so i’m right there in the same boat, but i’d try erasing the cpu since it is optional and see if that resolves it.

    Docker will be the best open platform for developers and sysadmins to build, ship, and run distributed applications.