[
https://issues.apache.org/jira/browse/MESOS-1524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14062485#comment-14062485
]
Vinod Kone commented on MESOS-1524:
-----------------------------------
Thanks for the doc [~tnachen]. Couldn't find a way to comment on the github
wiki, so commenting here.
Is the plan to kill ContainerInfo from CommandInfo in favor of DockerInfo?
What user is the docker container launched as? If its customizable, you need to
have a 'user' field in there.
Why do you need "repeated string args"? Why can't it be just part of the
"command" string?
What is the rationale for DockerInfo to be alongside CommandInfo instead of
replacing ContainerInfo?
> Implement Docker support in Mesos
> ---------------------------------
>
> Key: MESOS-1524
> URL: https://issues.apache.org/jira/browse/MESOS-1524
> Project: Mesos
> Issue Type: Epic
> Reporter: Tobi Knaup
> Assignee: Benjamin Hindman
>
> There have been two projects to add Docker support to Mesos, first via an
> executor, and more recently via an external containerizer written in Python -
> Deimos: https://github.com/mesosphere/deimos
> We've got a lot of feedback from folks who use Docker and Mesos, and the main
> wish was to make Docker a first class citizen in Mesos instead of a plugin
> that needs to be installed separately. Mesos has been using Linux containers
> for a long time, first via LXC, then via cgroups, and now also via the
> external containerizer. For a long time it wasn't clear what the winning
> technology would be, but with Docker becoming the de-facto standard for
> handling containers I think Mesos should make it a first class citizen and
> part of core.
> Let's use this JIRA to track wishes/feedback on the implementation.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
