copilot-cli: bug: Creating app runner services from ARM machines
Hi,
I’m following through the basic first app https://aws.github.io/copilot-cli/docs/getting-started/first-app-tutorial/. Everything goes along smoothly, but the ECS Service won’t deploy. I receive this message:
Resource handler returned message: "Error occurred during operation ECS Deployment Circuit Breaker was triggered'." (RequestToken: XXXXXXXXXXX, HandlerErrorCode: GeneralServiceException)
Would anyone know where I can review deployment logs? I checked on both copilot svc logs
and on AWS CloudWatch.
Here’s a full log output
- Creating the infrastructure for the example-app-test environment. [create complete] [81.7s]
- An IAM Role for AWS CloudFormation to manage resources [create complete] [24.6s]
- An ECS cluster to group your services [create complete] [6.4s]
- Enable long ARN formats for the authenticated AWS principal [create complete] [0.0s]
- An IAM Role to describe resources in your environment [create complete] [24.4s]
- A security group to allow your containers to talk to each other [create complete] [5.7s]
- An Internet Gateway to connect to the public internet [create complete] [13.9s]
- Private subnet 1 for resources with no internet access [create complete] [16.8s]
- Private subnet 2 for resources with no internet access [create complete] [16.8s]
- Public subnet 1 for resources that can access the internet [create complete] [16.8s]
- Public subnet 2 for resources that can access the internet [create complete] [16.8s]
- A Virtual Private Cloud to control networking of your AWS resources [create complete] [13.9s]
✔ Created environment test in region ap-southeast-2 under application example-app.
Environment test is already on the latest version v1.4.1, skip upgrade.
✔ Proposing infrastructure changes for stack example-app-test-front-end
- Creating the infrastructure for stack example-app-test-front-end [rollback complete] [866.2s]
The following resource(s) failed to create: [Service]. Rollback reques
ted by user.
- Service discovery for your services to communicate within the VPC [delete complete] [0.0s]
- Update your environment's shared resources [update complete] [114.2s]
- A security group for your load balancer allowing HTTP and HTTPS traffic [create complete] [5.0s]
- An Application Load Balancer to distribute public traffic to your services [create complete] [92.5s]
- An IAM Role for the Fargate agent to make AWS API calls on your behalf [delete complete] [2.4s]
- A CloudWatch log group to hold your service logs [delete complete] [2.4s]
- An ECS service to run and maintain your tasks in the environment cluster [delete complete] [57.8s]
Resource handler returned message: "Error occurred during operation 'E
CS Deployment Circuit Breaker was triggered'." (RequestToken: XXXXXXXXXXX, HandlerErrorCode: GeneralServiceExceptio
n)
Deployments
Revision Rollout Desired Running Failed Pending
PRIMARY 4 [failed] 1 0 9 1
- A target group to connect the load balancer to your service [delete complete] [2.4s]
- An ECS task definition to group your containers and run them on ECS [delete complete] [0.0s]
- An IAM role to control permissions for the containers in your tasks [delete complete] [2.4s]
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Reactions: 1
- Comments: 26 (12 by maintainers)
Commits related to this issue
- fix: redirect AppRunner services on ARM architectures to AMD (#2955) Previously, ARM -> AMD redirection was failing because we don't surface the `platform` field in RDWS manifests. Now we hard code ... — committed to aws/copilot-cli by huanjani 3 years ago
- fix: redirect AppRunner services on ARM architectures to AMD (#2955) Previously, ARM -> AMD redirection was failing because we don't surface the `platform` field in RDWS manifests. Now we hard code ... — committed to Lou1415926/copilot-cli by huanjani 3 years ago
@jsagorin hey, I had the same issue. I was able to fix it by installing docker desktop and deleting and re-initing the app.
Just make sure you have
docker
cli available when runningcopilot init
@.*** hello-app-runner-nodejs % copilot --version
copilot version: v1.11.0
@huanjani ^ ^
Hmm. So when I did:
DOCKER_DEFAULT_PLATFORM=linux/amd64 copilot init
It worked.