You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Yan Xu (JIRA)" <ji...@apache.org> on 2015/10/09 18:55:26 UTC

[jira] [Comment Edited] (MESOS-3688) Get Container Name information when launching a container task

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

Yan Xu edited comment on MESOS-3688 at 10/9/15 4:55 PM:
--------------------------------------------------------

He's saying that in your task if you read $MESOS_CONTAINER_NAME you'll get the container name. 

In fact, you can specify a custom environment variable when you launch the task/app and it'll get passed to the task itself (and you can have your task log it, have it be the first line in your log, etc.), then you'll be able to grep this in the log.

Will this help?


was (Author: xujyan):
He's saying that in your task if you read MESOS_CONTAINER_NAME you'll get the container name. 

In fact, you specify a custom environment variable when you launch the task/app and it'll get passed to the task itself (and you can have your task log it, have it be the first line in your log, etc.), then you'll be able to grep this in the log.

Will this help?

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