You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
... the documentation does not mention anything about my problem
... there are no open or closed issues that are related to my problem
Description
When using the latest version of buildx (0.11.2), if I run:
docker buildx build . --platform 'linux/amd64,linux/arm64' --push -t <my ECR repo url>, it creates a manifest list with MediaType v1+json, which is incompatible with AWS Elastic Container Repo.
Older versions of buildx (0.8.2) build a manifest list with the more up-to-date v2+json format, which is compatible with ECR.
Expected behaviour
Manifest list created by old buildx version (which is ECR compatible). Note the v2+json:
docker buildx imagetools inspect <image URL + tag from above>
Build logs
No response
Additional info
It's arguable whether this is a bug, but I imagine AWS ECR support is important to many docker users. Unless there's something unique about my setup, this issue creating multi-platform builds may be affecting a wide number of people.
The actual issue I see occurs when I try to build a model in sagemaker using the image (+ manifest list) uploaded to sagemaker. The error says `Unsupported manifest media type application/vnd.oci.image.index.v1+json for image . Ensure that valid manifest media type is used for specified image.
Thanks for reading!
The text was updated successfully, but these errors were encountered:
Set oci-mediatypes=false in your --output flag (to use the docker distribution manifest list instead of an OCI index).
This might cause some issues with the generated provenance, which means you'd probably prefer 3 instead.
Set --provenance=false to not generate the provenance (which is what causes the multi-platform index to be generated, even for a single platform).
Just remove the generated provenance entirely, this means that only a single manifest is created, no index needed, which sidesteps the problem.
Contributing guidelines
I've found a bug and checked that ...
Description
When using the latest version of buildx (0.11.2), if I run:
docker buildx build . --platform 'linux/amd64,linux/arm64' --push -t <my ECR repo url>
, it creates a manifest list with MediaType v1+json, which is incompatible with AWS Elastic Container Repo.Older versions of buildx (0.8.2) build a manifest list with the more up-to-date
v2+json
format, which is compatible with ECR.Expected behaviour
Manifest list created by old buildx version (which is ECR compatible). Note the
v2+json
:docker buildx imagetools inspect <redacted image url & tag>
Name: <redacted image url & tag>
MediaType: application/vnd.docker.distribution.manifest.list.v2+json
Digest: sha256:eb335f34c11fd2eaa57891c971424997773a00822f6b3f07fabf104af1d7e1fe
Manifests:
Name: <redacted image url & tag>@sha256:a494c5abb9d5d0af2e702bb123bf9ef6a31efab665f0e5261466525f629aa0ba
MediaType: application/vnd.docker.distribution.manifest.v2+json
Platform: linux/amd64
Name: <redacted image url & tag>@sha256:fe42b469678edecbb3a07c4f340673d912564e1e67bdc270227322ba9818884c
MediaType: application/vnd.docker.distribution.manifest.v2+json
Platform: linux/arm64
docker buildx version
github.com/docker/buildx v0.8.2 6224def
Actual behaviour
Manifest list created by latest buildx version (which is NOT ECR compatible):
Buildx version
github.com/docker/buildx v0.11.2 9872040
Docker info
Builders list
Configuration
docker buildx build . --platform='linux/amd64,linux/arm64' -f Dockerfile_test --push -t .dkr.ecr..amazonaws.com/:
docker buildx imagetools inspect <image URL + tag from above>
Build logs
No response
Additional info
It's arguable whether this is a bug, but I imagine AWS ECR support is important to many docker users. Unless there's something unique about my setup, this issue creating multi-platform builds may be affecting a wide number of people.
The actual issue I see occurs when I try to build a model in sagemaker using the image (+ manifest list) uploaded to sagemaker. The error says `Unsupported manifest media type application/vnd.oci.image.index.v1+json for image . Ensure that valid manifest media type is used for specified image.
Thanks for reading!
The text was updated successfully, but these errors were encountered: