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 bug is happening because when sending the artifact using flitp bundle push ...oras-go is setting the media type to application/vnd.oci.image.manifest.v1+json even flipt putting the value to application/vnd.io.flipt.features.v1 when creating the bundle artifact!
And the problem is, AWS will reject the bundle because it'll not be compliant with a Docker image as they states here:
The [OCI artifact specification](https://github.com/opencontainers/artifacts/blob/master/artifact-authors.md) defines artifact types, akin to file extensions, represented by the config.mediaType field of a manifest. For example, an OCI image, that is, something that you can use in Amazon EKS or Amazon ECS, would have a value of application/vnd.oci.image.config.v1+json. Custom types can also be defined, following the format:
Looking at the Oras documentation we can also see this problem can happen with Azure Container Registry too because AWS and Azure are the only ones where the examples explicit says to provide the --artifact-type option!
Bug Description
The bug is happening because when sending the artifact using
flitp bundle push ...
oras-go is setting the media type toapplication/vnd.oci.image.manifest.v1+json
even flipt putting the value toapplication/vnd.io.flipt.features.v1
when creating the bundle artifact!And the problem is, AWS will reject the bundle because it'll not be compliant with a Docker image as they states here:
Source: OCI Artifact Support In Amazon ECR
Looking at the Oras documentation we can also see this problem can happen with Azure Container Registry too because AWS and Azure are the only ones where the examples explicit says to provide the
--artifact-type
option!Source: Compatible OCI Registries
Version Info
The latest, I'm using the current commit from the main 😄
Search
Steps to Reproduce
Expected Behavior
No error when using AWS ECR or Azure Container Registry! For that we must also set the media type when sending the artifact to any OCI registry.
Additional Context
I'm already working on a fix for this!
The text was updated successfully, but these errors were encountered: