[
https://issues.apache.org/jira/browse/MESOS-1593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14069223#comment-14069223
]
Timothy Chen commented on MESOS-1593:
-------------------------------------
[~gabrtv] Let me respond to your comments in several pieces, but let me answer
few points you have:
We currently are using the docker name to record some metadata about the docker
running instance, which all mesos launched docker instances have names format
as "mesos-#{containerID}"
--ports is something to consider, will be curious what variations you like to
see supported and how that looks like in DockerInfo
(https://docs.docker.com/reference/run/#expose-incoming-ports)
DockerInfo will be supporting the standard Environment message as in
CommandInfo, and what you provide there will be passed in to docker run exactly
with -e flag. Our current code actually already supports this too, you just
need to provide Env variables in CommandInfo.
Docker auto rm/kill is supported already, and it follows the Mesos executor
lifecycle. Once a task is killed we automatically kill and rm the container for
you. In slave recovery we also reap the dangling docker containers that is not
checkpointed as well, so there shouldn't be any left running docker images.
> 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)
