Full Image Cache instantly completes
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- docker, go, kubernetes
- Domain
- build-system, devops, infrastructure
Research direction
Start with envbuilder.log and reproduce the Dockerfile plus config-file flow using full image caching, comparing the cache-hit launch with a manual pod using the cached image. Trace the envbuilder binary's entrypoint behavior after the full-image cache hit. Done means the cached image runs its entrypoint and all Dockerfile RUN commands instead of immediately completing.
Written by the indexing model from the issue text.
Description
We are running envbuilder to compile an image from a dockerfile and the config file.
Run without caching everything works as expected its just slow
Run with a cache repo, it creates the image, pushes the image and runs correctly ONCE.
Subsequent launches with the cache enabled will do the usual file extractions and start the image but the layers will not be correct, some of the run commands seemed to not have executed. For example a simple rm in a run command either did not run or the files were recreated by the base layer.
Run with full image caching the image gets a dry run and found in the cache (as long as i did it once with the layer cache)
Unfortunately the image immediately completes after that and the pod gets restarted by the deployment.
When i manually create a pod with the image from the cache repo it works, the envbuilder binary exists and all run commands got executed correctly.
Heres the log, everything looks perfectly fine if only it would execute the entrypoint properly
envbuilder.log
- Dominant language
- Go
- Stars
- 300
- Forks
- 64
- Avg merge
- 20m
- Merged PRs (30d)
- 1
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.
More from coder/envbuilder
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 90/100
coder/envbuilder#506 ·
-
envbuilder Feature
Difficulty 3/5 1-2 days Newbie friendliness 56/100
coder/envbuilder#492 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
coder/envbuilder#484 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 38/100
coder/envbuilder#483 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 38/100
coder/envbuilder#481 · 1 comment ·
All issues in coder/envbuilder
Similar issues
-
feature-request helm
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
gravitational/teleport#69785 ·
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
crossplane/crossplane#7859 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100