[
https://issues.apache.org/jira/browse/MESOS-6934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16811150#comment-16811150
]
Gilbert Song commented on MESOS-6934:
-------------------------------------
commit db917f639e2d05fcf493e87649f42ddd2abfeae0
Author: Andrei Budnik [email protected]
Date: Fri Apr 5 13:06:49 2019 +0200
Fixed use-after-free bug in Docker provisioner store.
Deferred lambda callback of the `moveLayers()` to the `StoreProcess`
to prevent use-after-free of the process object since the callback
refers to the `StoreProcess` class variable `flags`.
Review: https://reviews.apache.org/r/70405
> Support pulling Docker images with V2 Schema 2 image manifest
> -------------------------------------------------------------
>
> Key: MESOS-6934
> URL: https://issues.apache.org/jira/browse/MESOS-6934
> Project: Mesos
> Issue Type: Improvement
> Components: containerization
> Environment: https://reviews.apache.org/r/70288/
> https://reviews.apache.org/r/70289/
> https://reviews.apache.org/r/70290/
> https://reviews.apache.org/r/70291/
> Reporter: Ilya Pronin
> Assignee: Gilbert Song
> Priority: Major
> Labels: containerization
> Fix For: 1.8.0
>
>
> MESOS-3505 added support for pulling Docker images by their digest to the
> Mesos Containerizer provisioner. However currently it only works with images
> that were pushed with Docker 1.9 and older or with Registry 2.2.1 and older.
> Newer versions use Schema 2 manifests by default. Because of CAS constraints
> the registry does not convert those manifests on-the-fly to Schema 1 when
> they are being pulled by digest.
> Compatibility details are documented here:
> https://docs.docker.com/registry/compatibility/
> Image Manifest V2, Schema 2 is documented here:
> https://docs.docker.com/registry/spec/manifest-v2-2/
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
