Content trust sign with buildx
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 4.5k
- Forks
- 682
- Avg merge
- 2d 14h
- Merged PRs (30d)
- 29
Description
Hello,
Is there any way to sign a multi architectural image built by buildx?
The build is running like this:
docker buildx build --platform linux/amd64,linux/arm64 -t ${IMAGE}:${VERSION} --push .
To sign the image I am doing a regular "docker push" or "docker trust sign" but it signs and pushes only a local arch image and then overrides the manifest list previously pushed with buildx.
Somehow official hub.docker.com repo have signed multi-arch images, so how?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the issue with the listed docker buildx build command, then compare its multi-architecture manifest behavior with docker trust sign and a regular docker push. The issue mentions no source files or tests; done means identifying a supported signing workflow that preserves the pushed multi-architecture manifest.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go
- Domain
- devops, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100