concourse / concourse/docker-image-resource
Can't supply seperate Docker and AWS credentials
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 162
- Forks
- 250
- PR merge metrics
- No merged PRs in 30d
Description
Due to the docker rate limiting on downloads, when I am building an image from docker hub sources that I want to push to AWS ECR I am hitting the limit due the anonymous login.
Is there a way to specify docker credentials for the build step?
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 by tracing the build step that pulls Docker Hub sources before pushing to AWS ECR. Determine how credentials are currently supplied for each registry, then verify that separate Docker Hub and ECR credentials work without anonymous Docker Hub access; the issue names no files or tests to run.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, docker
- Domain
- cloud, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100