AWS re:Postを使用することにより、以下に同意したことになります AWS re:Post 利用規約
AWS re:Postre:Post

CodePipeline with ECS Fargate using Graviton2 is failing

1

I migrated my ECS Fargate workloads to Graviton2, however when I am using CodePipeline to release new code, it removes

"runtimePlatform": {
        "operatingSystemFamily": "LINUX",
        "cpuArchitecture": "ARM64"
    },

from the task definition and then the task fails due to architecture mismatch. I am using Amazon ECS as the deploy provider, so it only suppose to update the imageUri in the task definition. If I manually add the removed part, it works just fine.

  • ben
    2年前

    Hi Mark,

    We are also experiencing the same issue, I have raised a support ticket with AWS as there seems to be no way to keep the runtimePlatform when deploying.

トピック
開発者用ツールサーバーレスコンテナ
タグ
AWS CodePipelineAWS FargateAmazon Elastic Container Serviceコンテナ
言語
English
mark
質問済み 2年前543ビュー
3回答
0

Have you modified your CI to build multi-architecture images as highlighted in this blog post?

Jason_S
回答済み 2年前
  • mark
    2年前

    Hi Jason, I don't want multi-architecture containers, because it would mean 18 builds for a single application. My problem is that CodeDeploy is changing the task definition. My builds are fine.

0

Hi Mark,

Received this from AWS Support!

I just received an update from the CodePipeline service team. They mentioned that this is a known issue. The service team are busy working on a fix for this issue. I will be monitoring the ticket for an update and as soon as I receive an update, I will communicate the details with you. For now, I will be placing this case in the "Pending Amazon Action" state.

Hopefully it won't be long for a fix, have a good day.

Ben

ben
回答済み 2年前
  • mark
    2年前

    Hi Ben, Has it been fixed yet? Cheers, Mark

0

Hey, As the fails message says, you have mismatch configuration in your cpu Arch, look at your configuration files if everything is in order. Based on this aws doc, runtime is not required. Sometimes, providing this will trigger further checks and fails.

AWS
Zmnako
回答済み 2年前
  • mark
    2年前

    If I remove runtime then it will not use arm processors. If I change the imageUri manually (as Codedeploy suppose to do) it works fine.

ログインしていません。 ログイン 回答を投稿する。

優れた回答とは、質問に明確に答え、建設的なフィードバックを提供し、質問者の専門分野におけるスキルの向上を促すものです。

質問に答えるためのガイドライン

関連するコンテンツ