concourse / concourse/docker-image-resource
Using docker images from previous build stages
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 162
- Forks
- 250
- PR merge metrics
- No merged PRs in 30d
Description
When I build a Dockerfile containing a FROM instruction, the docker engine expects the image to be available (a reasonable assumption) however, the FROM image I'd like to use is from an earlier step in my build pipeline.
The problem is that the PUT step of the first image sets the image as repository/image:tag but my FROM instruction asks for image:tag
Using the load_bases config makes the repository/image:tag available, but it's not useable since it's technically a different image name. Is there a way to get around this?
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 how the Dockerfile FROM instruction, the first image's PUT step, and the load_bases config resolve image names. Check how repository/image:tag and image:tag are handled, then verify that an image produced by an earlier pipeline step can be referenced by the later FROM instruction under the requested name.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100