ECS updating service with same tasks but different docker image

I am an issue that either I do not understand well or something weird happening with aws ecs service.

I update my code, create a new docker image and push it to be deployed using ECS. The issue is, when the task definition does not changes, the code does not get deployed, even though the image in ECR got updated. How can get my code deployed then? I am assuming that when the image has changed, the services is run the already registered tasks which should pull the image right?

  • Elastic Beanstalk Multi-Container Environment cannot mount fuse mount as docker volume
  • Using pm2 Inside of an Auto-Scaling Environment
  • docker kill and capturing logs or buffers
  • Installing cPhalcon on AWS Docker Image
  • Can't login to docker with aws
  • Consul agent are still marked as in critical state after terminating whole instance
  • Example of commands I run

    aws ecs register-task-definition --cli-input-json file:///deploy/tasks/my-task-definition.json
    aws ecs update-service --service my-service --cluster my-clusdter --task-definition my-task-defintion

    The first time I run these commands, the code is deployed, if I update my code, push the new image to the Registry, then run these commands, my code does not get deployed.

  • Installing Python 3 Docker Ubuntu error command 'x86_64-linux-gnu-gcc
  • Using pm2 Inside of an Auto-Scaling Environment
  • Will single docker container scale automatically on Amazon's EC2?
  • Does Docker provide any memory efficiency on top of a VM?
  • Domain name setup to docker instance
  • AWS EC2 Container program command line arguments
  • Docker will be the best open platform for developers and sysadmins to build, ship, and run distributed applications.