I just spent some time to dig into this and it looks like we *will* be
impacted by this. I updated mesos-slave.conf in Vagrant to pass
--executor_environment_variables='{}' and as predicted by this pull
request: https://github.com/apache/aurora/pull/21, sys.executable is empty,
so we fail to fork the runner.Unfortunately even after applying that patch, there still seem to be issues with forking processes. I've filed https://issues.apache.org/jira/browse/AURORA-1632 to track the investigation and fixes so we're not blocked when Mesos 0.30.0 is released. ---------- Forwarded message ---------- From: Gilbert Song <gilb...@mesosphere.io> Date: Tue, Mar 8, 2016 at 1:33 PM Subject: Executors no longer inherit environment variables from the agent To: d...@mesos.apache.org, u...@mesos.apache.org Hi, TL;DR Executors will no longer inherit environment variables from the agent by default in 0.30. Currently, executors are inheriting environment variables form the agent in mesos containerizer by default. This is an unfortunate legacy behavior and is insecure. If you do have environment variables that you want to pass to the executors, you can set it explicitly by using the `--executor_environment_variables` agent flag. Starting from 0.30, we will no longer allow executors to inherit environment variables from the agent. In other words, `--executor_environment_variables` will be set to “{}” by default. If you do depend on the original behavior, please set `--executor_environment_variables` flag explicitly. Let us know if you have any comments or concerns. Thanks, Gilbert
