[
https://issues.apache.org/jira/browse/MESOS-10130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17111226#comment-17111226
]
Stéphane Cottin edited comment on MESOS-10130 at 5/19/20, 2:48 PM:
---
I made the same tests :)
The bug is on the nexus side, it did not respect the accept header and always
return manifest lists. I will create an issue in the Sonatype's jira.
Update: https://issues.sonatype.org/browse/NEXUS-23969
Btw, should manifest lists be supported by Mesos ? IMO It makes sense because
it run on multiple architectures.
was (Author: kaalh):
I made the same tests :)
The bug is on the nexus side, it did not respect the accept header and always
return manifest lists. I will create an issue in the Sonatype's jira.
Btw, should manifest lists be supported by Mesos ? IMO It makes sense because
it run on multiple architectures.
> Docker Manifest list support
>
>
> Key: MESOS-10130
> URL: https://issues.apache.org/jira/browse/MESOS-10130
> Project: Mesos
> Issue Type: Improvement
> Components: containerization
>Reporter: Stéphane Cottin
>Priority: Major
> Labels: containerization
>
> Sonatype Nexus 3.22+, and probably other docker registry solutions, now
> serves manifest lists.
> [https://issues.sonatype.org/browse/NEXUS-18546]
> Apache Mesos does not support yet this part of the Image Manifest V2S2 spec.
> https://docs.docker.com/registry/spec/manifest-v2-2/#manifest-list
> This is not a critical issue as Sonatype Nexus is not a dependency of Apache
> Mesos, but as we cannot use Nexus > 3.21.2, this leads to side security
> issues.
> [https://support.sonatype.com/hc/en-us/articles/360046233714]
> Apache Mesos should support the whole Image Manifest V2S2 specification.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
