By using AWS re:Post, you agree to the Terms of Use

deployment stuck "in progress" and docker-login. task failed

0

i am trying to deploy docker image which is stored in ECR using greengrass. but in one of my core i am not able to deploy it Job executions process stuck "In progress". and inside my core i have properly setup Security credentials and core as well. setup core

greengrass logs which is inside my core. Error inside Core located in /greengrass/v2/logs/greengrass.log

AWS status AWS status

So, i am struggling to figure out why this has happened and what i can do. Any ideas?

3 Answers
0

Hello,

I see your Docker images are stored in an Amazon ECR private repository, and you are encountering error when logging into ECR.

  1. Make sure that you installed the latest AWS CLI version 2. We recommend that you use the AWS CLI version 2. For more information, see Installing the AWS CLI in the AWS Command Line Interface User Guide.
  2. Be sure that you have included the token exchange service component as a dependency in the Docker container component. Also, verify the Greengrass device IAM role if it has proper permissions. It must allow the ecr:GetAuthorizationToken, ecr:BatchGetImage, and ecr:GetDownloadUrlForLayer actions, as shown in the following example IAM policy.
{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Action": [
        "ecr:GetAuthorizationToken",
        "ecr:BatchGetImage",
        "ecr:GetDownloadUrlForLayer"
      ],
      "Resource": [
        "*"
      ],
      "Effect": "Allow"
    }
  ]
}
answered 2 months ago
0

Hello, the error in your screenshots appears to be due to misconfiguration for docker and Greengrass does not deal with docker installation or configuration, you might try the few suggestions from https://github.com/docker/cli/issues/2229 , as described in this issue you may have golang-docker-credential-helpers installed which also needs pass installed. For your Greengrass deployment I believe this error occurs before the usage of TokenExchangeService for ECR login/image download, so as suggested by others on this question also make sure your policies and roles are correctly configured. Thanks.

answered 2 months ago
0

First thing I suggest for you to simulate your policy/role that is attached. See if it giving successful and denied. That will give you clue if it stopped in first place. https://policysim.aws.amazon.com/home/index.jsp?#

answered a month ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions