You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Jacob Janco (JIRA)" <ji...@apache.org> on 2019/05/01 23:07:00 UTC
[jira] [Commented] (MESOS-9760) Decouple Docker runtime isolator
manifest configuration from image provider
[ https://issues.apache.org/jira/browse/MESOS-9760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16831311#comment-16831311 ]
Jacob Janco commented on MESOS-9760:
------------------------------------
https://reviews.apache.org/r/70581/
> Decouple Docker runtime isolator manifest configuration from image provider
> ---------------------------------------------------------------------------
>
> Key: MESOS-9760
> URL: https://issues.apache.org/jira/browse/MESOS-9760
> Project: Mesos
> Issue Type: Improvement
> Components: agent, docker
> Reporter: Jacob Janco
> Assignee: Jacob Janco
> Priority: Minor
>
> The Docker runtime isolator propagates manifest configuration metadata. This is not always desirable, e.g. a customer may want to ignore the defined WORKDIR/ENV defined in the manifest.
> We propose adding a flag `–docker_ignore_manifest_config` to decouple the choice of Docker as an image provider and the need for the Docker runtime isolator. In the background, this flag will conditionally ignore the work of the Docker runtime isolator.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)