add per-arch digest to metadata file

Open
#4,080 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
docker, go
Domain
build-system, devops

Research direction

Start by tracing how buildctl produces the metadata file and how the existing containerimage.buildinfo/{platform} properties are assembled. Use the per-platform manifest digests already visible in buildctl logs as the reference, and consider the work done when each platform entry contains its corresponding containerimage.digest without changing the multi-arch digest.

Written by the indexing model from the issue text.

Description

When building/pushing a multi-arch image, the metadata file "containerimage.digest" refers to the digest of the multi-arch manifest. However, we have a need for the per-arch manifest digests. I can see they are reported in the logs from buildctl, but they are not included in the metadata file.

Please add a "containerimage.digest" property to each "containerimage.buildinfo/{platform}" property containing the manifest digest for that target platform.

Dominant language
Go
Stars
10.3k
Forks
1.5k
Avg merge
1d 23h
Merged PRs (30d)
48

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from moby/buildkit

All issues in moby/buildkit

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.