concourse / concourse/docker-image-resource

Provide credentials for base image different from the image to be built

Open
#278 2 comments 8 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
162
Forks
250
PR merge metrics
No merged PRs in 30d

Description

Hi,
i have the following setup:

Dockerfile of "child" image

FROM quay.io/team/base
...do something...

quay.io need authentication and the following would work as expected.

- name: docker-image-tools
    type: docker-image
    icon: docker
    source:
      repository: quay.io/team/base
      username: ((quay_username))
      password: ((quay_password))

Now I want to build the "child" image above, but push it to AWS ECR:

- name: docker-image-child
    type: docker-image
    icon: docker
    source:
      repository: account.dkr.ecr.region.amazonaws.com/child

When I execute that I get an error that authentication for quay.io is missing (what is basically OK).

But now the question:
Can I provide different credentials for the base image and the image to created/push? Or do i have to ensure that the base image and the target image are in the same repo?
I did not find anything related in the docs

Thanks in advance!

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or entry points are named. Start by reviewing the docker-image resource documentation and how source credentials are handled, then determine whether separate credentials can be configured for the base and destination images. Done means the supported behavior and configuration are documented, or the requested capability has an explicit implementation path.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, docker
Domain
cloud, devops
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.