Hi UnevenDolphin73

Took a long time to figure out that there was a specific Python version with a specific virtualenv that was old ...

NICE!

Then the task requested to use Python 3.7, and that old virtualenv version was broken.

Yes, if the Task is using a specific python version it will first try to find this one (i.e. which python3.7 ) then use it to create the new venv

As a result -> Could the agent maybe also output the 

virtualenv

 version used with setting up the environment for the first time?

You mean into the Log ? (I think you have all the log from the get go, no?!)

EDIT:

I also tried setting 

agent.python_binary: "/usr/bin/python3.8"

 but it still uses Python 2.7?

I think that in docker mode this argument is ignored, as the assumption is it will break inside diff containers.