aws / aws/aws-xray-daemon

Issues pulling XRAY Daemon image from Docker.io

Open
#162 3 comments 1 reaction 0 assignees View on GitHub
Dominant language
Go
Stars
193
Forks
73
Avg merge
2d 7h
Merged PRs (30d)
3

Description

Hi,

Our Terraform image dependency is defined like so :

```

sidecar_definitions = [{
name : "xray-daemon"
image: "amazon/aws-xray-daemon"
essential : false
portMappings : [
{
protocol : "tcp"
containerPort : 2000
},
{
protocol : "udp"
containerPort : 2000
}
]

logConfiguration : {
logDriver : "awslogs"
options : {
awslogs-group : aws_cloudwatch_log_group.xraydaemon.name
awslogs-region : var.aws_region
awslogs-stream-prefix : "amazon/aws-xray-daemon"
}
}
}]
```

When we deploy this in AWS cloud we're getting an error indicating that Docker.io image is not available (or at least that the response code for the request which is trying to pull it was not correct).

CannotPullContainerError: inspect image has been retried 5 time(s): httpReadSeeker: failed open: unexpected status code https://registry-1.docker.io/v2/amazon/aws-xray-daemon/manifests/sha256:e0a815332a9d64c0a1949ae755ed33907c37a4782713009325ea32ab9221...

The error is copied from ECS console.

What is the issue ? Is docker.io having problems ? Or AWS unpublished the image ?

Best Regards,
Rafal

Contributor guide

Open the contributing guide

Research direction

Start with the ECS CannotPullContainerError and the Terraform sidecar_definitions image reference shown in the issue. Check whether the amazon/aws-xray-daemon image and referenced digest are available from Docker.io, then determine whether a repository change is actually required; the issue does not name a source file, test, or concrete change.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, docker, terraform
Domain
cloud, devops
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.