[
https://issues.apache.org/jira/browse/MESOS-1593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14078857#comment-14078857
]
Jay Buffington commented on MESOS-1593:
---------------------------------------
Is {{has_entrypoint}} really necessary? Can you somehow inspect the image to
see if it has an entrypoint?
{{DockerInfo}} has a {{CommandInfo}}. If I specify {{URI}}s where will the
fetcher put them? It seems like the sanest thing to do is to fetch them into
the sandbox (just like always) and then bind mount the sandbox as the user's
home dir. This will also solve the "how do we get an executor into the docker
container" problem.
{{PublishPorts}} is a little strange. I realize you're just mapping the docker
interface into this protobuf, but ports are sort of special in mesos because
they are almost always a resource. That means that the caller would have to
specify the port twice: once in the {{TaskInfo}}'s {{Resource}} list and once
in {{PublishPorts}}'s {{host_port}}. And if the array of {{host_ports}} the
caller specifies aren't a subset of the ports listed in the {{TaskInfo}}'s
{{Resource}} list that should be an error. Also, {{PublishPorts}} is only
meaningful if network=BRIDGE
> Add DockerInfo Configuration
> ----------------------------
>
> Key: MESOS-1593
> URL: https://issues.apache.org/jira/browse/MESOS-1593
> Project: Mesos
> Issue Type: Task
> Reporter: Timothy Chen
> Assignee: Timothy Chen
>
> We want to add a new proto message to encapsulate all Docker related
> configurations into DockerInfo.
> Here is the document that describes the design for DockerInfo:
> https://github.com/tnachen/mesos/wiki/DockerInfo-design
--
This message was sent by Atlassian JIRA
(v6.2#6252)
