Full Image Cache instantly completes

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](https://github.com/user-attachments/files/25622697/envbuilder.log)

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

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