Full Image Cache instantly completes

未关闭
#495 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
35/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
停滞
技术栈
docker, go, kubernetes
领域
build-system, devops, infrastructure

调研方向

从 envbuilder.log 开始，使用完整的镜像缓存复现 Dockerfile 加 config-file 流程，并将 cache-hit 启动与使用缓存镜像的手动 pod 进行比较。跟踪完整镜像发生 cache-hit 后 envbuilder 二进制文件的 entrypoint 行为。完成的标准是，缓存镜像会运行其 entrypoint 和所有 Dockerfile RUN 命令，而不是立即完成。

由索引模型根据 Issue 内容生成。

描述

bug envbuilder needs-investigation

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

主要语言
Go
星标
300
派生
64
平均合并
20 分钟
30 天内合并 PR
1

贡献指南

这个仓库没有索引到贡献指南

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

coder/envbuilder 的其他 Issue

查看 coder/envbuilder 的全部 Issue

相似的 Issue

更多 Go Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。