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:
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.