buildkit 0.11 fails to push to interal registry but 0.10 works fine

[nemith]

When pushing a multiplatform build via buildx my coworkers reported issues while I had none. Looking at the difference I was running an older buildkit image and they were downloading 0.11.2.

I was able to repo by recreating my builder.

The registry was returning a 400 error with very little details. Registry is an internal registry and I am not sure what software it is actually running.

time="2023-02-03T20:37:40Z" level=debug msg="unexpected response" body="{\"errors\":[{\"code\":\"MANIFEST_INVALID\",\"message\":\"manifest invalid\",\"detail\":{}}]}\n" 

[crazy-max]

Can you post a repro with build command and a Dockerfile please? And a bit more logs (client and server) like #2479 (comment) would be appreciated.

Registry is an internal registry and I am not sure what software it is actually running.

Would be nice to know but best guess is the registry doesn't support the OCI spec. Error message looks similar to docker/buildx#1513 (comment) with GCR when exporting cache to the registry.

[nemith]

That is probably a good guess. It seems he different is probably application/vnd.oci.image.manifest.v1+json vs application/vnd.docker.distribution.manifest.list.v2+json

More logs is hard without exposing internal url/details. I can see if i can try to sanitize this but it will take time.

[crazy-max]

If you're using buildx 0.10, provenance is enabled by default which creates an OCI-compliant multi-platform image. You can disable provenance with --provenance=false.

More info about attestations: https://docs.docker.com/build/attestations/

[nemith]

--provenance=false seemed to do the trick although no clue how i would have ever found this on my own.

cleaned logs:
https://gist.github.com/nemith/1d7a99701a52805f36e3e1290af49cbd

[rdhatt]

FWIW, the docs for --provenance were just updated.