AWS ECS 任务因 Docker 超时错误而失败

Question

我创建了一个 ECS 集群（EC2 Windows + 网络）并尝试运行一个任务来开始运行我的 ECR（docker 映像），该任务一直显示“待处理”状态，一段时间后它会更改为“已停止”。 在验证任务容器内的状态时，状态更新为“DockerTimeoutError：无法转换为启动；等待 8 秒后超时”。

我尝试在互联网上查看 AWS 文档和其他博客/论坛，但都没有帮助解决我的问题。 我还按照本站点的建议为日志创建了一个端点 - https://charlesnagy.info/it/aws/aws-fargate-dockertimeouterror但这也没有帮助。

有没有人遇到过同样的问题，并且能够解决它？

下面添加了我的 VPC 设置、路由表、安全组的屏幕截图 -

任务设置 JSON 是 -

 { "ipcMode": null, "executionRoleArn": null, "containerDefinitions": [ { "dnsSearchDomains": null, "environmentFiles": null, "logConfiguration": null, "entryPoint": null, "portMappings": [ { "hostPort": 7189, "protocol": "tcp", "containerPort": 80 } ], "command": null, "linuxParameters": null, "cpu": 0, "environment": [], "resourceRequirements": null, "ulimits": null, "dnsServers": null, "mountPoints": [], "workingDirectory": null, "secrets": null, "dockerSecurityOptions": null, "memory": null, "memoryReservation": null, "volumesFrom": [], "stopTimeout": null, "image": "xxxxxxxxxxxxxxxxxxxxx.dkr.ecr.ap-south-1.amazonaws.com/xxxxxxxxapi", "startTimeout": null, "firelensConfiguration": null, "dependsOn": null, "disableNetworking": null, "interactive": null, "healthCheck": null, "essential": true, "links": null, "hostname": null, "extraHosts": null, "pseudoTerminal": null, "user": null, "readonlyRootFilesystem": null, "dockerLabels": null, "systemControls": null, "privileged": null, "name": "xxxxxxxxxxapi" } ], "placementConstraints": [], "memory": "512", "taskRoleArn": null, "compatibilities": [ "EXTERNAL", "EC2" ], "taskDefinitionArn": "arn:aws:ecs:ap-south-1:xxxxxxxxxxxx:task-definition/xxx-webapi-td:9", "family": "xxx-webapi-td", "requiresAttributes": [ { "targetId": null, "targetType": null, "value": null, "name": "com.amazonaws.ecs.capability.ecr-auth" } ], "pidMode": null, "requiresCompatibilities": [ "EC2" ], "networkMode": null, "cpu": "512", "revision": 9, "status": "ACTIVE", "inferenceAccelerators": null, "proxyConfiguration": null, "volumes": [] }