[
https://issues.apache.org/jira/browse/MESOS-7692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16056740#comment-16056740
]
Mao Geng commented on MESOS-7692:
---------------------------------
[~tillt] I found another issue today, not sure if it is same root cause.
Tfmesos, the framework based on HTTP Scheduler API to run tensorflow in docker
on mesos, couldn't submit tasks in Docker containerizer any more. Previously I
could run https://github.com/douban/tfmesos/blob/master/script/tfrun#L17 with
{{-C DOCKER}}, which would launch tasks by docker containerizer, however, on
mesos 1.3.0-2.0.3 the tasks were launched by mesos containerizer even with same
option and code.
Could you please help troubleshoot? Should I open a new ticket for that?
> Default environment variables defined in docker image are not available in
> mesos containerizer
> ----------------------------------------------------------------------------------------------
>
> Key: MESOS-7692
> URL: https://issues.apache.org/jira/browse/MESOS-7692
> Project: Mesos
> Issue Type: Bug
> Components: containerization
> Affects Versions: 1.3.0
> Reporter: Mao Geng
> Assignee: Till Toenshoff
> Priority: Blocker
> Fix For: 1.3.1
>
>
> Found an unexpected change in 1.3.0-2.0.3 - the environment variables defined
> by ENV statements in dockerfile are not available in mesos containerizer any
> more. For example LD_LIBRARY_PATH of tensorflow/tensorflow:latest-gpu image,
> JAVA_HOME of java:8 image, etc.
> The env vars are available in mesos containerizer in 1.2.0. Looks like a
> regression to me, isn't it?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
