[ 
https://issues.apache.org/jira/browse/MESOS-1524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14062423#comment-14062423
 ] 

Timothy Chen commented on MESOS-1524:
-------------------------------------

As [~benjaminhindman] described earlier we want to provide a DockerInfo message 
that describes all Docker specific settings that doesn't fit well in other 
Mesos settings. I've created a description that describes what DockerInfo will 
look like and some thinking we've done around DockerInfo here 
(https://github.com/tnachen/mesos/wiki/DockerInfo-design), and also created a 
new jira for this (MESOS-1593)
Will love more feedback around this especially on settings you like to see 
supported with Docker + Mesos, and please comment on that specific JIRA for 
more discussion on this.


> 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)

Reply via email to