Details
-
Task
-
Status: Resolved
-
Minor
-
Resolution: Fixed
-
1.6.0
-
Mesosphere Sprint 2018-21
-
1
Description
The issue is easily reproducible if one launches a task group and the taks nested container defines the same set of environment variables as the executor. In those circumstances, the following snippet is activated:
if (environment.contains(name) && environment[name] != value) {
cout << "Overwriting environment variable '" << name << "'" << endl;
}
But this is not the only time that this file writes into cout.
This may be a bad idea because applications which consume the standard output of a task may end up being corrupted by the container manager output. In these cases, writing to cerr should be the right approach.
