Error occured during operation 'ECS Deployment Circuit Breaker Was Triggered'
I'm trying to deploy a Docker application to ECS using Copilot and the Load Balanced Web Service, but I keep running into this error:
Resource handler returned message: "Error occurred during operation 'E
CS Deployment Circuit Breaker was triggered'." (RequestToken: 121161f9
-1c97-e3d5-b4d3-8328bb2b676c, HandlerErrorCode: GeneralServiceExceptio
n)
I tried checking the logs and got:
describe service demo-app: no active ECS service found
Any idea how to fix this issue? Here is my Dockerfile settings:
# syntax=docker/dockerfile:1.4
FROM directus/directus:10.8.3
USER root
RUN corepack enable \
&& corepack prepare [email protected] --activate \
&& chown node:node /directus
EXPOSE 8055
USER node
CMD : \
&& node /directus/cli.js bootstrap \
&& node /directus/cli.js start;
Hello @0xJamin !
sorry for the trouble.
Does the service already exists and you are updating the service or Is it for the first time you are deploying this service?
Can you go to CloudFormation console and check the status of status.
whether it is in UPDATE_ROLLBACK_FAILED state ?
Hi @KollaAdithya this is the first time I'm running the service, and CloudFormation consoles shows ROLLBACK_COMPLETE
@0xJamin
- Which version of copilot are using ?
Can you try running copilot svc deploy command again.
-
Does the command error out immediately?
-
Or does the terminal shows
Proposing infrastructure changes for stack xxxxxsomething like this
✔ Proposing infrastructure changes for stack biggboss-sid-lbwsfirelens
- Updating the infrastructure for stack biggboss-sid-lbwsfirelens [update in progress] [42.1s]
- Update your environment's shared resources [update complete] [5.9s]
- An HTTP listener rule for path `/` that redirects HTTP to HTTPS [not started]
- A custom resource assigning priority for HTTP listener rules [not started]
- An HTTPS listener rule for path `/` that forwards HTTPS traffic to your tasks [not started]
- A custom resource assigning priority for HTTPS listener rules [not started]
- The default alias record for the application load balancer [not started]
- An ECS service to run and maintain your tasks in the environment cluster [update in progress] [21.5s]
Deployments
Revision Rollout Desired Running Failed Pending
PRIMARY 16 [in progress] 1 0 0 1
ACTIVE 15 [completed] 1 1 0 0
- An ECS task definition to group your containers and run them on ECS [update complete] [3.8s]
If the CloudFormation stack deployment is in progress and go to ECSConsole-> Service->tasks-> stopped tasks -> reason and see why it fails and share over here
No, it doesn't.
It shows the error and rolls back everything. I've tried running over and over again, but the same thing.
I ended up deploying the application with an EC2 instance instead
Which version of Copilot are you using?
While the deployment is going on, Can you do ⏬
Go to ECSConsole-> Service->tasks-> stopped tasks -> reason and see why ECS task fails and share over here
This issue is stale because it has been open 60 days with no response activity. Remove the stale label, add a comment, or this will be closed in 14 days.
This issue is closed due to inactivity. Feel free to reopen the issue if you have any further questions!