- Newest
- Most votes
- Most comments
Hi Gwen,
is the app healthy? Typically the circuit breaker is triggered when the app does not bootstrap correctly and is deemed as unhealthy.
Start looking into this: https://repost.aws/knowledge-center/ecs-task-container-health-check-failures
Hope it helps
Hi @alatech, thank you so much for your help. I resolved the issue greatly owing to your lead.
To benefit other members in the future, here's how I solved it:
-
- Tested the docker file locally.
-
- Turns out, I provided NONE of the env variables in the Dockerfile which are used across my backend app.
-
- I hard-coded the env variables in the Dockerfile.
-
- Uploaded the Dockerfile WITH env vars to ECR.
-
- Tasks are now running on ECS fine and pretty, no problem!
Thank youuu :D
-
I had the same problem as you. I suggest you to check the service status ,such as "Essential container in task exited" <Exit code: 1>
I built my image on an M1 Mac, then pushed it to ECR (AWS’s version of Docker Hub) for running via ECS, which was using an x86 architecture. To summarise the problem, docker images built for the M1 chip won't work on x86 machines because the way the chips are built is different. Just like a puzzle piece made for a square puzzle won't fit in a round puzzle. The Docker image has been made to fit one type of puzzle (M1 chip), but it won't fit in the other type of puzzle (x86 machine). Link : https://www.padok.fr/en/blog/essential-container-error-ecs
This was my case too, after building the image with windows everything works fine.. avoid building image with M1 Chip (apple silicon)
Hi, I had a similar issue and found the root cause by looking into the Cloud Trail logs.
I'm posting this as an answer as I believe it may help anyone having issues with the too general 'GeneralServiceException', no matter which resource one is trying to deploy by using CloudFormation.
Go to CloudTrail -> "Event History" and go to "Preferences" -> "Select visible columns" -> enable "Error code". Then filter the list to find the relevant event. If you enter the event and look at the JSON view, you should be able to find a field called "errorMessage", which holds more detailed information as to what have gone wrong.
Relevant content
- Accepted Answerasked 5 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 3 years ago
I get the same thing - and everything got deleted so there is no way to follow up on the 'health checks'. IN addition, I dont have this problem using http, only when trying to setup https. FARGATE is a great obfuscator.