[
https://issues.apache.org/jira/browse/MESOS-3688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14978314#comment-14978314
]
Raffaele Di Fazio commented on MESOS-3688:
------------------------------------------
I saw that in some parts of the code there's already a "multiple support" for
docker ID generated in different ways, I don't see any issue in using the same
logic until the old way of representing the container id will be removed from
the code. The issues we could have are probably already affecting other parts
of code (see parse function in docker.cpp).
> Get Container Name information when launching a container task
> --------------------------------------------------------------
>
> Key: MESOS-3688
> URL: https://issues.apache.org/jira/browse/MESOS-3688
> Project: Mesos
> Issue Type: Improvement
> Components: containerization
> Affects Versions: 0.24.1
> Reporter: Raffaele Di Fazio
> Assignee: Kapil Arya
> Labels: mesosphere
>
> We want to get the Docker Name (or Docker ID, or both) when launching a
> container task with mesos. The container name is generated by mesos itself
> (i.e. mesos-77e5fde6-83e7-4618-a2dd-d5b10f2b4d25, obtained with "docker ps")
> and it would be nice to expose this information to frameworks so that this
> information can be used, for example by Marathon to give this information to
> users via a REST API.
> To go a bit in depth with our use case, we have files created by fluentd
> logdriver that are named with Docker Name or Docker ID (full or short) and we
> need a mapping for the users of the REST API and thus the first step is to
> make this information available from mesos.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
