- 최신
- 최다 투표
- 가장 많은 댓글
Have you modified your CI to build multi-architecture images as highlighted in this blog post?
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.
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
Hi Ben, Has it been fixed yet? Cheers, Mark
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.
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.
관련 콘텐츠
- AWS 공식업데이트됨 일 년 전
- AWS 공식업데이트됨 일 년 전
- AWS 공식업데이트됨 일 년 전
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.