You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am running the command, it goes in and "updates" the task definition, but with the original image name. It just re-deploys the same image, doesn't update it to the one I specify? 🤔
Using image name: strm/helloworld-http:latest
Current task definition: arn:aws:ecs:us-east-1:xxxx:task-definition/just-another-test:3
New task definition: arn:aws:ecs:us-east-1:xxxx:task-definition/just-another-test:4
Service updated successfully, new task definition running.
Waiting for service deployment to complete...
Service deployment successful.
But when I check in ECS, the service/tasks are running on the new version, but it still has their original image name set in the task definition. Confused.
The text was updated successfully, but these errors were encountered:
Even weirder, it works just fine if I set the image as -i "nginx:latest". Once that completed, I tried again with -i "strm/helloworld-http" but the image remains as nginx:latest on the new task definition it generates 😖
| sed -e 's~"image":.*'"${imageWithoutTag}"'.*,~"image": "'"${useImage}"'",~g' \
The sed that does the search and replade does not error out if there is no match, it just fails silently doing nothing.
The fix would be to print an error if there is not match for the image provided to the ecs-deploy.sh script.
Am I missing something silly here?
I am running the command, it goes in and "updates" the task definition, but with the original image name. It just re-deploys the same image, doesn't update it to the one I specify? 🤔
Running:
I get:
But when I check in ECS, the service/tasks are running on the new version, but it still has their original image name set in the task definition. Confused.
The text was updated successfully, but these errors were encountered: