[
https://issues.apache.org/jira/browse/MESOS-3866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15398420#comment-15398420
]
Steven Schlansker commented on MESOS-3866:
------------------------------------------
We just independently rediscovered this bug -- since the containerizer sets the
version agent side, if you are in a "live upgrade" situation where you upgrade
the agent but not the library baked into your containers yet, an otherwise safe
upgrade turns into a breaking change!
> The docker containerizer sets MESOS_NATIVE_JAVA_LIBRARY in docker executors
> ---------------------------------------------------------------------------
>
> Key: MESOS-3866
> URL: https://issues.apache.org/jira/browse/MESOS-3866
> Project: Mesos
> Issue Type: Bug
> Components: containerization
> Affects Versions: 0.25.0
> Reporter: Michael Gummelt
>
> It's set here:
> https://github.com/apache/mesos/blob/master/src/slave/containerizer/containerizer.cpp#L281
> And passed to the docker executor here:
> https://github.com/apache/mesos/blob/master/src/slave/containerizer/docker.cpp#L844
> This leaks the host path of the library into the docker image, which of
> course can't see it. This is breaking DCOS Spark, which runs in a docker
> image that has set its own value for MESOS_NATIVE_JAVA_LIBRARY.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
