Mar*_*ger 5 networking amazon-web-services amazon-ecs aws-fargate
我正在尝试使用 ECS Fargate 设置几个服务,这些服务通过 Terraform 进行配置。它们使用相同的模块,只是镜像、ALB 目标组、环境变量和端口映射不同。
3 个服务中的 2 个成功启动了他们的任务,只有一个(不幸的是主服务),不想启动并Network bindings - not configured为容器显示。我使用的端口是80。
任务定义具有正确的端口映射。
我试过更改端口(到 8080),使用多个端口映射并多次重新创建服务,但没有任何效果。
当然,由于运行状况检查失败,该任务会被负载均衡器终止。
任何指针可能是错误的?我从 2017 年开始发现了一些与此相关的 Github 问题,但在 EC2 支持的 ECS 实例上,已声称已修复。
作为参考,这里是任务定义 JSON:
{
"ipcMode": null,
"executionRoleArn": "ROLE_ARN",
"containerDefinitions": [
{
"dnsSearchDomains": null,
"logConfiguration": {
"logDriver": "awslogs",
"secretOptions": null,
"options": {
"awslogs-group": "/drone",
"awslogs-region": "eu-central-1",
"awslogs-stream-prefix": "drone-server/"
}
},
"entryPoint": null,
"portMappings": [
{
"hostPort": 80,
"protocol": "tcp",
"containerPort": 80
}
],
"command": null,
"linuxParameters": null,
"cpu": 256,
"environment": [...],
"resourceRequirements": null,
"ulimits": null,
"dnsServers": null,
"mountPoints": [],
"workingDirectory": null,
"secrets": [...],
"dockerSecurityOptions": null,
"memory": 512,
"memoryReservation": 512,
"volumesFrom": [],
"stopTimeout": 30,
"image": "drone/drone:1",
"startTimeout": null,
"dependsOn": null,
"disableNetworking": null,
"interactive": null,
"healthCheck": null,
"essential": true,
"links": null,
"hostname": null,
"extraHosts": null,
"pseudoTerminal": null,
"user": null,
"readonlyRootFilesystem": false,
"dockerLabels": null,
"systemControls": null,
"privileged": null,
"name": "drone-server"
}
],
"placementConstraints": [],
"memory": "512",
"taskRoleArn": "ROLE_ARN",
"compatibilities": [
"EC2",
"FARGATE"
],
"taskDefinitionArn": "TASK_DEFINITION_ARN",
"family": "drone-server",
"requiresAttributes": [
{
"targetId": null,
"targetType": null,
"value": null,
"name": "com.amazonaws.ecs.capability.logging-driver.awslogs"
},
{
"targetId": null,
"targetType": null,
"value": null,
"name": "ecs.capability.execution-role-awslogs"
},
{
"targetId": null,
"targetType": null,
"value": null,
"name": "com.amazonaws.ecs.capability.docker-remote-api.1.19"
},
{
"targetId": null,
"targetType": null,
"value": null,
"name": "com.amazonaws.ecs.capability.docker-remote-api.1.21"
},
{
"targetId": null,
"targetType": null,
"value": null,
"name": "com.amazonaws.ecs.capability.task-iam-role"
},
{
"targetId": null,
"targetType": null,
"value": null,
"name": "ecs.capability.container-ordering"
},
{
"targetId": null,
"targetType": null,
"value": null,
"name": "ecs.capability.secrets.ssm.environment-variables"
},
{
"targetId": null,
"targetType": null,
"value": null,
"name": "com.amazonaws.ecs.capability.docker-remote-api.1.18"
},
{
"targetId": null,
"targetType": null,
"value": null,
"name": "ecs.capability.task-eni"
}
],
"pidMode": null,
"requiresCompatibilities": [
"FARGATE"
],
"networkMode": "awsvpc",
"cpu": "256",
"revision": 14,
"status": "ACTIVE",
"proxyConfiguration": null,
"volumes": []
}```
Run Code Online (Sandbox Code Playgroud)
显然 Fargate 不太擅长报告错误或显示状态。它不会在 AWS 控制台中显示所有环境变量或正确的状态,但无论如何都能工作。
这个故事的主旨是,如果控制台中没有显示某些内容,请务必测试它是否实际上不起作用。
老实说,我无法告诉我的问题的解决方案,因为当我通过环境变量在 Drone CI 服务器上打开跟踪日志记录时,它就消失了。
| 归档时间: |
|
| 查看次数: |
4864 次 |
| 最近记录: |