-
Notifications
You must be signed in to change notification settings - Fork 503
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
Buildx 0.10.0 giving additional manifest to docker image? #1507
Comments
i got null manifest push |
Looks related to #1509 (comment) |
This is the new provenance feature, which is enabled by default - you can get the contents using $ docker buildx imagetools inspect <your-image> --format '{{ json .Provenance }}' To disable it on build, you can explicitly set |
so sad, this default value broken our pipeline which follow the page https://www.docker.com/blog/multi-arch-build-and-images-the-simple-way/, the |
@debu99, thanks for the feedback 👍 The article you link to is slightly out of date at this point - while it does work, you might also be interested in being able to do multi-platform builds even more simply using buildx: https://docs.docker.com/build/building/multi-platform/ |
@debu99 the |
@thaJeztah jinx 🎉 |
we tried |
To merge manually, I'd recommend still using buildx: $ docker buildx imagetools create -t <dest> <source1> <source2> <source3> ... If you're building using buildx, it makes sense to do the merge using it as well - specifically it properly handles merging indexes correctly. I think for your use case, it should be a drop-in replacement. @debu99, you can also do native builds using the |
coming from docker/build-push-action#755, as it actions builds that may lead to different solving method. I agree with such feature, it just caught me surprised that some In my comprehension, revert to Thanks for detailed informations. |
I saw notable changes on 0.10.0 about
Notable changes
Build command supports new flags --attest and shorthands --sbom and --provenance for adding attestations for your current build. --attest type=sbom or --sbom=true will generate SBOM (Software Bill of Materials) attestation for your build result in SPDX format. --attest type=provenance or --provenance=true will generate SLSA provenance attestation for your build result with information about how the build was performed. When creating OCI images a minimal provenance attestation is included with the image by default. This feature requires BuildKit v0.11.0+. Read more about advanced SBOM options from BuildKit docs. Attestations from buildx #1412 buildflags: error on duplicate attest field #1475
When building with BuildKit that supports provenance attestations Buildx will automatically share the version control information of your build context so it can be shown in provenance for later debugging. Previously this only happened when building from a Git URL directly. To opt-out of this behavior you can set BUILDX_GIT_INFO=0. Optionally you can also automatically define labels with VCS info by setting BUILDX_GIT_LABELS=1. build: set provenance vcs details #1462 Add git provenance labels #1297 [1340] Disable git labels if
BUILDX_GIT_LABELS
is not1
orfull
#1341 build: fix env vars check for vcs details #1468 build: lookup the right git binary on WSL #1477Named contexts with --build-context now support oci-layout:// protocol for initializing the context with a value of a local OCI layout directory. E.g. --build-context stagename=oci-layout://path/to/dir. This feature requires BuildKit v0.11.0+ and Dockerfile 1.5.0+. build: refactor reference parsing for oci image layouts #1456
I think one of the notable somehow create some unknown manifest?
I tried
BUILDX_GIT_INFO=0
but doesnt affect. My question is, what is the correct way to disable it?Thanks.
The text was updated successfully, but these errors were encountered: