Cache images based on dockerfile contents
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 13.8k
- Forks
- 1.4k
- Avg merge
- 17h 58m
- Merged PRs (30d)
- 5
Description
When creating a new repository based on a template and then launching Gitpod from the new repository, the user has to wait for the docker image to be built. This can take quite a while.
What if Gitpod could fingerprint the dockerfile contents used and cache the image based on that? Then the image would just need to be pulled as long as the user does not change the dockerfile.
I am working on a template project for the Exercism.org Clojure track. And the whole story would get so much better without the long wait for building the image.
Here's the template: https://github.com/PEZ/clojure-exercism-template
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
Begin by locating Gitpod's Docker image build and retrieval flow for a new template repository; no files or entry points are named in the issue. Done means unchanged Dockerfile contents reuse a previously built image, while changed contents cause a new image build.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- 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