Improve Docker image build speeds by utilizing a cache
Open
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 1
- Forks
- 1
- Avg merge
- 17h 48m
- Merged PRs (30d)
- 1
Description
Every time a Docker build runs in CI, it's building the entire image from scratch. Surely we can figure out a way to utilize a cache to speed up the build speeds.
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
Start by reviewing the repository's CI configuration and Docker image build steps to determine how builds currently run without a cache. Compare available Docker caching approaches and verify the result in CI. Done means repeated Docker builds reuse cached layers instead of rebuilding the entire image and build speed improves.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- ci-cd, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100