[
https://issues.apache.org/jira/browse/MESOS-7692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16056672#comment-16056672
]
Till Toenshoff commented on MESOS-7692:
---------------------------------------
[~jieyu] yup, I am tackling that.
The scenario however is even broader and unfortunately still not covered by our
tests...
What that bug did was that it was serializing environment data in the wrong
format -- jsonified hashmap instead of jsonified Environment proto. This
serializing happens when being forwarded as a task specific (not executor
inherited) environment towards the command executor {{task_environment}}. As a
result no task specific environment variables were forwarded. Such task
specific environment could come e.g. from a runtime isolator (docker). So the
reported issue is just one manifestation of a bad bug in our very unfortunately
complex data flow towards the command executor.
> 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)
