You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@mesos.apache.org by "Jie Yu (JIRA)" <ji...@apache.org> on 2016/05/29 22:32:12 UTC

[jira] [Updated] (MESOS-5465) Container image as a volume source should also include image manifest.

     [ https://issues.apache.org/jira/browse/MESOS-5465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jie Yu updated MESOS-5465:
--------------------------
    Shepherd: Jie Yu

> Container image as a volume source should also include image manifest.
> ----------------------------------------------------------------------
>
>                 Key: MESOS-5465
>                 URL: https://issues.apache.org/jira/browse/MESOS-5465
>             Project: Mesos
>          Issue Type: Bug
>            Reporter: Jie Yu
>            Assignee: Guangya Liu
>
> Currently, if a user specifies the source of a volume to be an image (e.g., Docker image), we only prepare the rootfs and mount it at 'container_path' in the container.
> However, the rootfs itself is not sufficient to allow the executor to launch the docker container. We need the docker manifest as well to get the env, entry point, cmd information.
> One solutions is to make container_path a directory containing two things: 1) rootfs, 2) manifest. But this is a breaking change, we might need to introduce a deprecation cycle for that.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)