-
Notifications
You must be signed in to change notification settings - Fork 509
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Content trust sign with buildx #313
Comments
Hi @tonistiigi |
For anyone finding this issue, the solution to sign a manifest is to use the So, you will need to use buildx to push tags like |
Notary is so much user unfriendly, abandoned and overcomplicated solution that after being using it since 2017 with both Docker Hub and a private registry we decided to stop using it. |
Has anything moved forward with this? Having a first class way to build and sign multi-platform releases in a single command would be a REALLY great way to increase adoption of Docker Content Trust |
Using the notary scripts is way too fragile and complicated for me to use. I would expect something like I would really like to be able to sign all 5 as well. |
Hello, this was opened in 2020 and since then I can't find any information on it. |
You will find more than you can ever need on https://github.com/sudo-bot/action-docker-sign |
Is signing multi-arch images still so complicated? Our CI/CD workflows build and push for multiple arch, with a single tag. From there, how can we sign both images that share the same tag? I would expect |
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?The text was updated successfully, but these errors were encountered: