mesos-reviews mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Joseph Wu <>
Subject Re: Review Request 56341: Changed docker/runtime isolator's handling of Environment.
Date Tue, 07 Feb 2017 22:17:56 GMT

This is an automatically generated e-mail. To reply, visit:

(Updated Feb. 7, 2017, 2:17 p.m.)

Review request for mesos, Jie Yu and Kevin Klues.


Moved the command executor changes into another review, to keep those logically separate.

Bugs: MESOS-7027

Repository: mesos


This commit adds more special-casing in the `docker/runtime` isolator
for the command executor.  The command executor will generally break
when the `docker/runtime` isolator provides environment variables
directly to the executor.  This is because the environment variables
are provided in the context of the container image, rather than the

For example, a container image may provide an environment variable
like `LD_LIBRARY_PATH=/image/specific/location`, whereas the default
executor expects to find libraries in the host's environment.  If the
image's environment end up in the command executor at launch time, 
the command executor may simply fail to launch.

Diffs (updated)

  src/slave/containerizer/mesos/isolators/appc/runtime.cpp 9bc3fd8309435846c17944e74f611212069dbd76

  src/slave/containerizer/mesos/isolators/docker/runtime.cpp 2d816e512c95ed2922c9578ba796908c5ce23da4



make check

sudo src/mesos-tests --gtest_filter="*ROOT*"

All the tests broken by (earlier in the chain) are now


Joseph Wu

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message