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

Jay Buffington commented on MESOS-1524:
---------------------------------------

It seems like there are three approaches:

    # shelling out to docker cli (what deimos does)
    # using the [docker REST 
api|https://docs.docker.com/reference/api/docker_remote_api_v1.12/]
    # linking against docker itself

#1 is probably a bad idea because the docker CLI is a porcelain interface and 
would be difficult to maintain due to changes in the user facing command line 
tool.

#2 would send HTTP request containing JSON to dockerd.  There would need to be 
a command line option to point to dockerd endpoint.

#3 is complicated by fact that the docker is written in Go and there don't seem 
to be any C++ bindings

Other approaches?

> 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