stackabletech / stackabletech/docker-images
Use docker contexts for fetching sources (where possible)
Nobody has claimed this yet.
- Dominant language
- Dockerfile
- Stars
- 22
- Forks
- 6
- Avg merge
- 16h 59m
- Merged PRs (30d)
- 30
Description
Docs: https://docs.docker.com/build/bake/contexts/
This should let us get rid of a bunch of redundant downloading code, but more importantly make it easier to patch out components ("use this local jmx-exporter sources instead of downloading the pinned version from git").
Contributor guide
No contributing guide indexed for this repository
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
Read the Docker Build contexts documentation linked in the issue first. No files, tests, or entry points are named, so locate the source-fetching and downloading logic across the repository's Docker image builds. Done means redundant downloading is removed where Docker contexts support it and local component sources can replace pinned downloads.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- build-system
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100