我正在使用 .NET Core WEBAPI 和以下 Dockerfile
FROM microsoft/dotnet:sdk AS build-env
WORKDIR /app
# Copy csproj and restore as distinct layers
COPY *.csproj ./
RUN dotnet restore
# Copy everything else and build
COPY . ./
RUN dotnet publish -c Release -o out
# Build runtime image
FROM microsoft/dotnet:aspnetcore-runtime
WORKDIR /app
COPY --from=build-env /app/out .
ENTRYPOINT ["dotnet", "DummyService.dll"]
在我的cloudformation模板中,ECS部分是这样的
dummyWebApiEcsTaskDefinition:
Type: AWS::ECS::TaskDefinition
Properties:
Family: !Ref AWS::StackName
TaskRoleArn: !GetAtt dummyWebApiIamRole.Arn
ContainerDefinitions:
- Name: !Ref AWS::StackName
Image: MY IMAGE URL
DnsSearchDomains:
- !Join [".", [{"Fn::ImportValue": !Sub "${accountStackName}-${AWS::Region}-envName"}, "connected", !If [chinaPartition, "TEST", "CORP"], "cloud"]]
LogConfiguration:
LogDriver: splunk
Options:
splunk-token: {"Fn::ImportValue": !Sub "${splunkHECStackName}-${AWS::Region}-SplunkHECToken"}
splunk-url: "http://splunk-forwarder:8088"
splunk-insecureskipverify: True
tag: !Ref AWS::StackName
splunk-format: json
splunk-source: !Ref AWS::StackName
splunk-sourcetype: AWS:ECS
EntryPoint: []
PortMappings:
- ContainerPort: 5000
Command: []
Cpu: 0
Environment:
- Name: BindAddress
Value: http://0.0.0.0:5000
- Name: MinLogLevel
Value: !If [isProduction, "Information", "Debug"]
Ulimits: []
DnsServers: []
MountPoints: []
DockerSecurityOptions: []
Memory: 512
VolumesFrom: []
Essential: true
ExtraHosts: []
ReadonlyRootFilesystem: false
DockerLabels: {}
Privileged: false
dummyEcsService:
Type: AWS::ECS::Service
DependsOn:
- dummyWebApiIamRole
- dummyInternalAlb
- dummyAlbTargetGroup
Properties:
Cluster:
Fn::ImportValue: !Sub "cld-core-ecs-${AWS::Region}-ECSCluster"
DeploymentConfiguration:
MaximumPercent: 200
MinimumHealthyPercent: 50
DesiredCount: 2
LoadBalancers:
- ContainerName: !Ref AWS::StackName
ContainerPort: 5000
TargetGroupArn: !Ref dummyAlbTargetGroup
PlacementStrategies:
- Type: spread
Field: attribute:ecs.availability-zone
TaskDefinition: !Ref dummyWebApiEcsTaskDefinition
ServiceName: !Ref AWS::StackName
Role: !Sub "arn:${AWS::Partition}:iam::${AWS::AccountId}:role/aws-service-role/ecs.amazonaws.com/AWSServiceRoleForECS"
部署无法完成,我可以在 ECS 服务事件选项卡中看到此错误
service cld-dummy-test was unable to place a task because no container instance met all of its requirements. Reason: No Container Instances were found in your cluster.
最佳答案
我终于明白了这一点。下面的错误消息表明该集群中没有 EC2,因此无法启动任何容器。我们没有使用 Fargate。
service cld-dummy-test was unable to place a task because no container instance met all of its requirements. Reason: No Container Instances were found in your cluster.
要将 EC2 注册到集群,您需要遵循这篇 AWS 文章。
https://docs.aws.amazon.com/AmazonECS/latest/developerguide/launch_container_instance.html
请注意,您启动的 EC2 需要具有以下用户数据才能注册。
#!/bin/bash
echo ECS_CLUSTER=your_cluster_name >> /etc/ecs/ecs.config
完成上述操作后,您应该不会看到“无容器”的错误信息。但是,如果您像我一样,在模板中有 splunk 日志记录部分。你会遇到一个不同的问题,它说没有容器可以用于任务,因为它缺少一个属性。这是一个相当模糊的消息,属性可以是任务定义页面底部列出的任何内容。
就我而言,它是 splunk 日志记录。需要将 splunk 驱动程序添加到 EC2 实例。由于我后来发现我们不再需要 splunk,所以我删除了 splunk 部分。但是如果你想这样做,你可能需要将下面的行添加到你的用户数据中。
ECS_AVAILABLE_LOGGING_DRIVERS=["splunk","awslogs"]
我希望这可以帮助别人。
关于amazon-web-services - AWS ECS 无法放置任务,因为没有容器实例满足其所有要求,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/55120107/