publish "image source" in the registry
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 15/100
- Issue 类型
- 功能
- 描述清晰度
- 需要澄清
- 活跃度
- 停滞
- 技术栈
- docker, git, go
- 领域
- build-system, release
调研方向
Start by reading the linked tarscrub.go filter in docker-library/bashbrew to understand what a filtered build context would contain, then inspect the scripts in this repo that generate source IDs and build IDs. Trace where BuildKit provenance is assembled and where the Dockerfile is currently embedded, since that is the insertion point for a published build-context tarball. Done means a documented, testable path for attaching the filtered context to image provenance, with a decision recorded on whether to pre-publish tarballs.
由索引模型根据 Issue 内容生成。
描述
The current BuildKit provenance objects we include have the full Dockerfile in them, but it's buried and obscured -- it would be really interesting for us to include the full build context somewhere in the registry/image provenance, especially after we implement https://github.com/docker-library/bashbrew/blob/f71d6ef63e1f5abe6d5cb06a62a3e5e42d68566e/pkg/tarscrub/tarscrub.go#L10 (because it could then be the "filtered" version of the build context, so it's literally just the elements that went into the build).
IMO building off that same tarball would then be even more meaningful than the current build-from-Git-URL that we do, and would also have the benefit of being generally more performant (since we'd be able to more directly control the Git fetching bits).
We could also do crazy things like pre-publish those tarballs and build directly from the published tarballs instead of doing the Git fetching at image build time, but that might be a step too far.
- 主要语言
- Go
- 星标
- 19
- 派生
- 24
- 平均合并
- 8 天 22 小时
- 30 天内合并 PR
- 1
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
docker-library/meta-scripts 的其他 Issue
-
难度 5/5 一周以上 新手友好度 10/100
docker-library/meta-scripts#141 ·
-
难度 5/5 一周以上 新手友好度 20/100
docker-library/meta-scripts#139 · 1 条评论 ·
-
难度 5/5 一周以上 新手友好度 12/100
docker-library/meta-scripts#138 · 1 条评论 ·
查看 docker-library/meta-scripts 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 84/100
github/github-mcp-server#3865 ·
维护者通常 2 天内回复
-
kind/features
难度 2/5 1-3 小时 新手友好度 75/100
TencentBlueKing/bk-nodemgr#4017 ·
维护者通常 1 天内回复
-
ssa: wait errors drop the kstatus message, so health check failures don't say why可能已有人在做 @schdief 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 76/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 76/100
equinor/radix-operator#2066 ·
维护者通常 2 天内回复
-
难度 2/5 1-3 小时 新手友好度 67/100
microsoft/terraform-provider-msgraph#188 · 1 个 reaction ·
维护者通常 1 天内回复