Open bdehamer opened 7 months ago
Hey @bdehamer , I believe the section relevant to the break here is actually 4.3 in the RFC spec: https://datatracker.ietf.org/doc/html/rfc6838#section-4.3
I've confirmed internally this is likely a bug on our side, and we'll let you know when we've rolled out a fix.
Hi @kattmang is there ETA for this fix?
Community Note
Tell us about your request I'd like for ECR to be less strict about the media type value which are accepted in the
artifactType
and layermediaType
fields in the image manifest.Which service(s) is this request for? ECR
Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard? I'm trying to push the following manifest into ECR:
The response I get is:
The issue appears to be the
;version=0.2
portion of my media type -- if I remove that parameter, the manifest can be uploaded successfully.Are you currently working around this issue? The only work-around I have at the moment is to re-write my media type strings and remove the
version
parameter, but this is critical data I'd rather not lose.Additional context The OCI image spec has the following to say about the
artifactType
field:RFC 6838 includes support for media type parameters (~section 4.4~section 4.3) so it would seem that my media type is compliant with the spec.
Related: https://github.com/aws/containers-roadmap/issues/308