docker / docker/github-builder
Provenance issue with public repository
还没有人认领这个 Issue。
- 主要语言
- 没有语言数据
- 星标
- 83
- 派生
- 23
- 平均合并
- 2 天 22 小时
- 30 天内合并 PR
- 8
描述
Contributing guidelines
- I've read the contributing guidelines and wholeheartedly agree
I've found a bug, and:
- The documentation does not mention anything about my problem
- There are no open or closed issues that are related to my problem
Description
Hello,
My repository is public (https://github.com/nsphung/mcp-snowflake-server/blob/main/Dockerfile). And from my understanding, using docker/github-builder (docker/github-builder/.github/workflows/build.yml@7d2a02426d4b989616ba5aaee4e879afd4134b0d # v1.6.0), it should use docker/buildx provenance = mode=max,version=v1. But I don't have the expected results.
Expected behaviour
This is what I have without using docker/github-builder:
docker buildx imagetools inspect nsphung/mcp-snowflake-server-nsp:0.8.0 --format "{{ json .Provenance.SLSA }}"
# This one is working
This was build with:
docker buildx build \
--tag nsphung/mcp-snowflake-server-nsp:0.8.0 \
--sbom=true \
--attest type=provenance,mode=max,version=v1 \
.
Is there any way to have the same feature in docker/github-builder ? Or maybe I'm missing a configuration.
Actual behaviour
docker buildx imagetools inspect nsphung/mcp-snowflake-server-nsp:0.11.2 --format "{{ json .Provenance.SLSA }}"
null%
Here we can see null when inspecting for provenance.
Repository URL
https://github.com/nsphung/mcp-snowflake-server/tree/main
Workflow run URL
https://github.com/nsphung/mcp-snowflake-server/actions/runs/25457043001
YAML workflow
You can checkout the yaml at:
https://github.com/nsphung/mcp-snowflake-server/blob/main/.github/workflows/publish.yml#L176
Workflow logs
No response
BuildKit logs
Additional info
No response
贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
调研方向
从 .github/workflows/publish.yml 第 176 行附近和固定在 v1.6.0 的 .github/workflows/build.yml 开始,然后将它们的构建配置与可正常工作的 docker buildx 命令进行比较。复现该工作流,并使用 docker buildx imagetools 检查生成的镜像;当支持的配置或限制得到确定,并且 provenance 行为得到记录或修正后,该 issue 即完成。
由索引模型根据 Issue 内容生成。
评估
- 技术栈
- docker, github-actions
- 领域
- ci-cd, devops, security
- Issue 类型
- 缺陷
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 活跃度
- 冷清
- 描述清晰度
- 基本清楚
- 新手友好度
- 45/100