Using credsStore (amazon-ecr-credential-helper) for pull/run commands
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 7.2k
- Forks
- 1.7k
- Avg merge
- 13d 8h
- Merged PRs (30d)
- 2
Description
Hello, is there a way to use amazon-ecr-credential-helper when running a new container? Currently I'm getting:
docker.errors.APIError: 500 Server Error for http://mydockerserver:2375/v1.43/images/create?tag=mytag&fromImage=xxxx.dkr.ecr.us-east-1.amazonaws.com%2Ffoo: Internal Server Error ("Head "https://xxxx.dkr.ecr.us-east-1.amazonaws.com/v2/foo/manifests/mytag": no basic auth credentials"
On mydockerserver docker pull works using AWS_PROFILE:
AWS_PROFILE=myawsprofile docker run xxxx.dkr.ecr.us-east-1.amazonaws.com/foo:mytag
Success
Same "no basic auth credentials" error I'm obtaining on mydockerserver when AWS_PROFILE=myawsprofile is not supplied.
So basically passing AWS_PROFILE into the execution context on the remote docker server should resolve the problem, right?
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
Start with the images/create API entry point used by the pull and run commands, then review how remote Docker Engine requests receive registry credentials. Compare this with amazon-ecr-credential-helper and AWS_PROFILE behavior; done means documenting or implementing a supported way to authenticate ECR image pulls on the remote server.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, docker, python
- Domain
- api, authentication, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100