concourse / concourse/docker-image-resource
Problem fetching the latest image in ECR
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 162
- Forks
- 250
- PR merge metrics
- No merged PRs in 30d
Description
Hi all,
I’m actually using this resource type to get a image from ecr to use in a PUT step, but it is actually failing with this error in this PUT step:
waiting for docker to come up...
Pulling xxxxxxxxxxxxx.dkr.ecr.us-east-1.amazonaws.com/my-image-name@sha256:xxxx01234567890987654322...
Error response from daemon: manifest for xxxxxxxxxxxxx.dkr.ecr.us-east-1.amazonaws.com/my-image-name@sha256:xxxx01234567890987654322 not found
Pulling xxxxxxxxxxxxx.dkr.ecr.us-east-1.amazonaws.com/my-image-name@sha256:xxxx01234567890987654322 (attempt 2 of 3)...
Error response from daemon: manifest for xxxxxxxxxxxxx.dkr.ecr.us-east-1.amazonaws.com/my-image-name@sha256:xxxx01234567890987654322 not found
Pulling xxxxxxxxxxxxx.dkr.ecr.us-east-1.amazonaws.com/my-image-name@sha256:xxxx01234567890987654322 (attempt 3 of 3)...
Error response from daemon: manifest for xxxxxxxxxxxxx.dkr.ecr.us-east-1.amazonaws.com/my-image-name@sha256:xxxx01234567890987654322 not found
Failed to pull image xxxxxxxxxxxxx.dkr.ecr.us-east-1.amazonaws.com/my-image-name@sha256:xxxx01234567890987654322.
fetching the image did not produce a volume
the resource type configuration :
- name: notifier
type: docker-image
source:
repository: xxxxxxxxxxxxx.dkr.ecr.us-east-1.amazonaws.com/my-image-name
It seems that it’s trying to retrieve an image that doesn’t actually exist.
The sha256 didn’t correspond to the latest version of this image. (the custom resource is configured to get the latest by default, ad even if use the tag parameter, it doesn't change nothing).
I’ve tried to do a manuel check of this resource to try to refresh it, but it fails with the same.
Tryed to delete the workers thinking about a local cache into them, but unsuccessful.
Any other kind of cache in the Postgresql database ? Any idea ?
Thanks a lot
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source file or test is named. Start by reproducing the docker-image resource configuration against the stated AWS ECR repository and compare the resolved digest with the manifest available in ECR; done means the latest image or supplied tag resolves to an existing manifest and the PUT step completes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, docker
- Domain
- cloud, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100